- Getting Started
- Example deployment to Heroku
- Using pipelines
- Deploying with Snap
- How do I add SSH keys to my build?
- Scheduling and skipping builds
- Deleting or cancelling a build run
- Billing owner best practices
- Deployment Pipeline
- The CI Environment
- Snap CI's Stacks
- Simple Docker pipeline using Snap CI
- Building & propagating Docker images
- Deploying Docker images
- Docker FAQ
- Known Limitations
- Relational Databases
- NoSQL Datastores
- Testing with browsers
- Complete Package List
- Environment Variables
- Heroku Deployments
- Deploying to AWS
- Deploying to AWS OpsWorks
- Deploying to AWS S3
- Deploying to AWS ElasticBeanstalk
- Working with Branches
- Cloning a pipeline
- Integration pipelines
- Automatic branch tracking
- Pull Requests
- Configuring multiple workers
- Speeding up builds
- Setting up test parallelism
- Pipeline Parallelism
- Polling project status using CCTray
- Webhook notifications
- How Snap integrates with GitHub
- Revoking privileges granted to Snap CI
- Managing membership
- Triggering Pipelines and Stages
- Migration to GoCD
- Migration to other CI and CD tools
Integration pipelines provide additional information for builds which track pipelines that are intended to be merged into a target branch (master) at some point in their lifecycle. Typically these are short lived feature branches or bug fix branches which are meant to merge quickly into a master branch. While this feature is best used in conjunction with the automatic branch tracking feature, it is available when setting up any branch build using the clone functionality.
Setting up an integration pipeline when creating a clone
- Visit the configuration page of the pipeline you wish to clone.
- Click on the clones link which will bring up the clone dialog.
- Select the appropriate branch from the first drop down.
From the second drop down, select the branch that the work is intended to be merged into.
This will set up an integration pipeline which will be triggered on successful completion of the primary pipeline. The integration pipeline is triggered with the branch changes merged with the HEAD of the integration target branch.
Review the stages cloned for the new pipeline.
Note: Keep in mind that the integration pipeline will be triggered after the last stage of the branch pipeline as it was originally configured. You can always add stages after that stage on the branch pipeline, but the integration pipeline will still trigger at the end of the stage that originally terminated the branch pipeline.
Integrated clones, running
While the integration pipeline runs, or if either pipeline fails, the build history page shows both pipelines expanded.
When a pipeline run or passes, the two pipelines collapse to conserve space. You can see the information about either pipeline by switching between the tracking-pipeline & integration-pipeline tabs.