With ShuttleOps, you can design deployment 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 deployment process.
ShuttleOps makes it easy to automate your deployments. Automatically start a deployment pipeline when an application component is updated in your artifact 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 acknowledgement is required at the start of the workflow. If the acknowledgement is received, the application components will be deployed to an AWS cloud environment. This pipeline includes a trigger to launch the pipeline automatically after a build pipeline has been successfully executed.
Click the Deploy tab, then click.
You’ll start with a basic pipeline that contains a start node, an Application Components node, and a finish node. Depending on your connections, the pipeline may also have an AWS, GCP or Azure public cloud destination node.
It’s important to note that a deployment pipeline must have one Applications Components node and one public cloud destination node (AWS, GCP or Azure). A pipeline cannot have multiple Applications Components nodes or multiple destination nodes.
Edit the Pipeline Name
When you first create a pipeline, it’s simply called “Deploy 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 deployment 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.
Application Components Add the application components you want to deploy. Note that your deployment pipeline can only contain one Application Components node.
Destinations Use destinations to deploy application components to public cloud providers including Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Note that your deployment pipeline can only contain one destination node.
Notifications Automatically send emails and Slack messages during the deployment 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 deployment pipeline. Just drag a trigger from the side panel and drop it on the start node. You can use the following types of triggers.
Chef Habitat Builder Launch the deployment pipeline automatically if an application is updated in the artifact 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 Deploy tab. You can use this tab to execute the pipeline at any time.