Start a pipeline from a preset or another project
Instead of building a project's pipeline stage by stage, start from a preset — a ready-made shape — or copy the pipeline of another project in your organization. Either one only fills in the custom pipeline: nothing changes until you select Save, so you can review and adjust it first.
Who can do this: anyone who may edit the project. Others see the pipeline read-only, without Start from….
Not available while the project is linked to a template: unlink first.
The presets
| Preset | Stages | What it is for |
|---|---|---|
| Standard | Ideas → Building → Dev → Production | The default. Merging deploys to Dev by itself; a release moves Dev to Production (main). |
| Trunk → Prod | Ideas → Building → Production | Merging deploys straight to Production: the integration branch is Production, and there is no release step. |
| Dev → Staging → Prod | Ideas → Building → Dev → Staging → Production | Two releases: Dev to Staging (staging), then Staging to Production (main). |
| Ideas only (no deploys) | Ideas | One stage, for planning. The only preset a project without a repository can take. |
Building uses the project's own branch prefix, such as fleet/*, and the first stage with a branch
uses the project's own integration branch, such as develop. Every step starts by hand with no approvals,
except merging, which runs by itself.
The pipeline a new project starts with
New project asks nothing about the pipeline. Jaah picks it from your answers:
| You are making | Starts with |
|---|---|
| A new app or website | Standard |
| A new business initiative | Ideas only |
| Anything in an existing repository | Standard, then the project's first task sets the stages the repository really deploys: a stage per branch the team ships from, or Ideas only where it deploys nowhere |
Change it any time in the project's Settings › CI Pipeline. If a pipeline breaks one of your org's pipeline rules, the project shows on the Pipeline rules card among the projects breaking it, to fix in its Settings › CI Pipeline.
Replace a project's pipeline with a preset
- Open the project, then Settings › CI Pipeline in its settings.
- Select Start from…, then A preset….
- Pick a preset. What changes lists each stage added (+) or removed (−) and each changed setting, such as "Production · Branch: main → integration branch".
- Select Use this. The editor shows the new stages with "Unsaved changes from …".
- Check the stages, change anything you like, then select Save. Discard goes back to the saved pipeline.
A stage whose name stays the same keeps its place in the project: the tasks on it stay where they are.
If a stage's branch is already used by another stage — for example Production on main when
the integration branch is main — the reason shows on that stage's card before you save: change its
branch, then Save.
Copy another project's pipeline
- Open the project, then Settings › CI Pipeline in its settings.
- Select Start from…, then Copy from project….
- Pick the project to copy from. The list shows every other project of your organization you can see, each with its stages; type in Search projects to narrow a long list.
- Review What changes, then select Use this and Save.
A copy takes the other project's stage names, branches and step settings: who may do each step, the approvals it needs and whether it runs by itself. It does not take:
- Addresses — they point at the other project's environments. A stage you already had keeps its own address; a new stage has none until you add it.
- Freezes — they stay as they are on this project.
- The integration branch and branch prefix — this project keeps its own.
Projects of other organizations are never listed and can't be copied.
Related
- Every stage and step setting: Set up a project's pipeline.
- Every field of the custom pipeline: Projects.