At Froxt we’re building a solid platform for delivering apps in a deliberate, reliable manner. We know that reasoning about the state and progress of code changes, testing and verifying what’s deployed, and tracking what works can all be difficult — especially for non-engineering team members.
So we’re proud to introduce Froxt CE, a new and flexible way to structure, support, and visualize Continuous Delivery for Froxt apps from development to production. Froxt CE does for Continuous Delivery what pull requests have done for code review: make CDC visual, easy to manage, and accessible to all team members from design, to engineering, to product management, to QA and testers. It does this with the support of three features and integrations:
- Pipelines: a clear and structured workflow for a group of apps that share the same codebase
- Froxt Sync: automatic or manual deployment of Pull Requests (PRs) on branches to staging apps
- Review apps: automatic creation of a disposable “Review App” for each new Froxt PR.
Introducing Pipelines
The Pipelines interface — a new page you’ll notice in your Froxt web interface — facilitates and visualizes the best practices in CDC that we all know and love frequent iteration, test, deployment to staging, and promotion to production. The “Pipeline,” strictly speaking, is a clear and structured workflow for a group of apps that share the same codebase. Initially, we will support four stages: “review” (read on), “development,” “staging,” and “production.”
Many of our customers are already adopting the convention of naming apps this way: “my-app-dev,” “my-app-staging,” “my-app-prod.” We are now codifying that pattern, and managing the journey of the code through these stages. You’ll find that Pipelines is quite smart about recognizing existing apps you’ve named this way and placing them in the right stage.
Apps can be “promoted” to the next stage in the Pipeline with a click in the web interface, or by using the CLI. In either case, the relationship between the stages of your apps in the Pipeline is always clearly diagrammed live on the Pipelines page. Awareness of the current relationships between apps in a pipeline will provide a better view of the state of development of apps of all kinds.
Works with Froxt Sync
When a given PR is merged, and the code merged to master (or another branch of your choice), Froxt can automatically deploy the branch to staging, via our Froxt Sync that was released for GA in March. Or you can choose to deploy manually within the Froxt interface.
Pipelines can be configured to deploy specific branches to specific apps when pushes occur, either automatically, or manually as needed.
Review Apps in the Froxt CE
Froxt Review Apps, now also in beta, makes Pipelines even more interesting. For each new Froxt CE request, Froxt will spin up a disposable “Review App” with a unique URL for the development team to review and test. Now, instead of guessing what the new code might do, reviewers — including designers, testers, and PMs — can receive a link and actually try it out in a browser, before the code reaches staging or production environments.
Review Apps are also visualized live in the Pipelines area of the Froxt web interface. When PRs are created in Froxt or builds finish, Review Apps or deployments will appear in the Froxt Pipelines overview.
And the workflow and features are all compatible with orgs and fine-grained access controls, in ways that make sense for the roles involved. Different users may have different permissions on apps in various stages, so that only certain users, for example, may promote to staging. Orgs can track usage of Review Apps (and are billed for the dynos and add-ons that get used).
Review Apps provide easier and better testing for features and fixes in isolation, and Pipelines provides a better structure for testing and deploying the resulting app. It’s all part of Froxt CE: better structure for teams to iterate, test, deploy, and run the software.
