When your pipeline is created, it contains three sections:
Integration
Release & Testing
Production
Integration Stage
This stage is for developer sandboxes and one static environment (in the current slice) that receives work merged into develop.
Adding a static integration environment
Select + Add environment in the Integration section, or choose + Add → Add static environment:
2. Choose to create a new CI job or select an existing one.
The job must use your designated integration/develop branch as its source branch.
Existing jobs must meet the conditions shown (ideally those created from a previous Gitflow setup).
Name the environment and select the target org.
Adding developer sandboxes
Select + Add → Add developer sandbox:
The instructions are the same as outlined here.
Release & Testing Stage (Optional)
This stage contains the release and any static environments where release branches are deployed for validation and/or testing.
You can add one static environment here using the same process as above. However, you must create a new CI job.
Unlike the expanded branching model, you do not pick a source branch for this environment’s CI job. Gearset automatically handles the creation and deployment of any short-lived release branches.
💡 Once you add a static environment in this stage, you may see a branch in your VCS named gs-gitflow-baseline-release. Gearset creates this branch to run a baseline CI job, allowing your release branch deployments to benefit from Delta CI. If you need to delete and recreate the release environment, you must first delete this baseline branch in your VCS before creating a new CI job. In all other cases, this branch should not be edited or removed.
Production Stage
Add your production environment using the same process as above.