With ShuttleOps, you can design build workflows based on your business rules and processes. Use approvals and acknowledgements to direct the workflow down different paths. And keep your team up-to-date by automatically sending email and Slack notifications throughout the build process.
ShuttleOps makes it easy to automate your builds. Automatically start a build pipeline when code is updated in your source control repository or schedule a pipeline to start at a specific time. You can also automatically execute a sequence of pipelines. This allows you to run dependent or related pipelines one after another, with no manual intervention required.
Let’s look at an example. In this pipeline, an approval process is an integral part of the workflow. If approval isn’t received, the pipeline stops running. If approval is received, the build is started. You’ll notice in the workflow that a Slack message is sent if the build is successful and an email is sent if the build fails. This pipeline is also scheduled to execute at a specific time.
Click the Build tab, then click.
You’ll start with a basic pipeline that contains a start node, a Code node, and a finish node. You’ll see that a Code node always has two branches. The workflow will follow the branch if all of the applications in the Code node are built successfully, and will follow the branch if at least one of the application builds fails.
Edit the Pipeline Name
When you first create a pipeline, it’s simply called “Build Pipeline”. Once you add application components, the name changes to the first component (alphabetically) included in the pipeline. If the same component exists in multiple build pipelines, a number is added to the pipeline name.
To customize the pipeline name, just click the name in the editor and change it.
Add Nodes and Branches
To build your workflow, drag a node from the side panel and drop it on a branch. When you hover over a branch,will appear to show where you can drop the node.
You can add the following types of nodes.
Code Add application components to include in the build.
Notifications Automatically send emails and Slack messages during the build process.
Gates Add quality gates to enforce your business rules and workflows. You can require an acknowledgement or approval from a user, team, or organization before the pipeline can proceed to the next step. You can also pause the pipeline at any time during the workflow.
Stop Automatically stop the pipeline at any point in the workflow. For example, you might want to stop the pipeline if an approval isn’t received.
You can start a new branch anywhere in the pipeline. Just hover over an existing branch, then click. Selectthen select the type of node you want to add to the branch. (For a description of the node icons, take a look at the side panel in the editor.)
You can use a trigger to automatically execute a build pipeline. Just drag a trigger from the side panel and drop it on the start node. You can use the following types of triggers.
On Push Automatically start the pipeline when an application component is updated in your source control repository.
Pipeline Automatically start the pipeline after another build or deployment pipeline has successfully executed.
Scheduled Schedule the pipeline to run at a specific time.
Execute the Pipeline
When you’re done, select Launch to execute the pipeline. If you don’t want to execute the pipeline right now, select the Build tab. You can use this tab to execute the pipeline at any time.