v1

Release /

Continuous integration and delivery on Northflank

Northflank enables you to manage your application delivery from development, through testing, to production.

You can automate builds and deployments using CI/CD in individual services, or use pipelines to configure workflows with complex tasks covering many resources.

You can also learn more in the guide on releasing for production.

Continuous integration and delivery

Continuous integration (CI) allows you to automatically build code when a commit is pushed to your Git repository. Continuous delivery (CD) automatically deploys new builds, in any environment.

You can configure rules in services and jobs to manage your development workflows and releases.

CI/CD on Northflank can be used to set up simple but powerful release flows. You can enable CI/CD in a single combined service in order to automatically build and deploy from one repository. You could also use CI/CD with a build service to build development, release, and production branches and deploy to different deployment services.

Release with pipelines

To manage more complex workflows you can use pipelines. You can add resources to different pipeline stages for visibility, and to make them available in release flows for that stage.

Release flows

Release flows are templates for specific pipeline stages that can automate release tasks, such as backing up databases, triggering builds, running jobs, and promoting images from one stage to another.

You can make each step in a release flow conditional so that if a step fails, the rest of the release will not continue. You can also quickly roll back to a previous release.

Triggering releases

Releases can be run manually, or you can configure a Git or webhook trigger to start a release flow run.

Run database migrations

You can run database migrations manually, or automate the process as part of a release flow.

Ephemeral preview environments

You can define a template to create ephemeral environments to preview Git branches or pull requests.

Preview environments can be created automatically using Git or webhook triggers, and torn down in one action.

Release using Git

You can store release flows as JSON in a Git repository and trigger a release when you commit changes to your release flow template.

You can also trigger releases using a webhook in a GitHub action.

© 2024 Northflank Ltd. All rights reserved.