After you define development environments and a release (production) org, you have a basic pipeline. However, it’s not recommended that you deploy directly to production. You can use our template to build the pipeline, you can add more stages to the pipeline template, or you can build your own.
While you’re working on building the pipeline, your changes persist but don’t get saved to the project until you activate the pipeline.
Complete the creation of the environments associated with each pipeline stage.
Important Although you can use the same source control repository across DevOps
Center projects, be sure the branches for each project are unique. If you re-use branches across
projects, you risk overwriting changes and introducing conflicts.
- Access the Pipeline page.
- From within the project, click Pipeline.
- From the All Projects page, click Click to Create Pipeline.
In the Pipeline page, you see the pre-defined pipeline template.
- Before you begin, it’s important to understand how to properly specify the branch for each
pipeline stage.
We recommend that you don’t share branches across projects.
- Complete your pipeline configuration using the preferred method.
- Use the provided template to build your pipeline.
- Build your own pipeline configuration.
For best results:
- Stage names can’t contain backslashes or double quotes.
- Follow recommended practices when naming the branches associated with each pipeline stage.
- If you’re using the same source control repository as another DevOps Center project, branches must be unique for each pipeline stage, except for the release branch (often called main). DevOps Center can’t track changes across projects so unique branches ensure that conflicts don’t get introduced and changes don’t get overwritten.