Managing pipelines
Cruise is configured using an XML configuration file. This file can be edited through the Cruise server dashboard. Cruise allows you to edit sections of the configuration independently and will check the syntax of the configuration before it saves it again. You can also edit the full XML file if you wish, by clicking on the Source XML section of the Administration tab.
Creating a new pipeline
To create a new pipeline, go to the pipelines configuration section of the Administration tab and click on the "Add new pipeline" link at the top right of the page.
Add a new stage to an existing pipeline
The easiest way to add a new stage is to copy an earlier stage and modify it. That's what we'll do here
- Click on the Administration tab
- Edit the pipeline
- Copy the original stage
- Paste it in the pipeline and edit the name and details as appropriate
- Click save
Add a new job to an existing stage
The easiest way to add a new job is to copy an earlier job within the stage and modify it. That's what we'll do here
- Click on the Administration tab
- Edit the stage
- Copy the original job
- Paste it in the stage and edit the name and details as appropriate
- Click save
Stage approvals in action
By default, when one stage completes successfully, the next stage is automatically triggered by Cruise. However sometimes you don't want the next stage to be triggered automatically. This might be the case if you have a stage that deploys your application to a testing, staging or production environment. Another case can be when you don't want your pipeline to be automatically triggered by changes in version control. In these situations, you want the stage triggered by manual intervention. This can be done through manual approvals.
If you add a manual approval to the first stage in a pipeline, it will prevent the pipeline from being triggered from version control. Instead, it will only pick up changes when you trigger the pipeline manually (this is sometimes known as "forcing the build").
From Cruise 1.1, you can control who can trigger manual approvals. See the section on Adding authorization to approvals for more details.
Managing pipeline groups
Starting with Cruise 1.3, the professional edition includes support for collecting multiple pipelines into a single named group. See the section on Specifying who can view and operate pipeline groups for more details.
