When you deploy an application using Quick Launch, ShuttleOps creates and runs a pipeline that includes automated steps to build, deploy, and manage your application to a secure environment. A pipeline can include multiple steps, decision points, forks, and approvals. 

You can use an application’s pipeline to check each step in the deployment process or to troubleshoot deployment issues.

Viewing Pipelines and Jobs

Click PIPELINES in the navigation bar.

The pipelines for each deployed application are shown. The following information is shown for each pipeline:

Pipeline Name  Application name.

Environment  Environment where the application is deployed.

No. of Jobs  Number of times the pipeline was executed.

Last Commit by  Person who last made a code change to the application component.

Last Updated  Date that the last commit was made.

State  Current pipeline state (e.g. active, inactive).

Each time a pipeline is executed, a job is created to track the pipeline activities. Click a pipeline to view the jobs that have been run for the pipeline. The following information is shown for each job:

Job No.  Unique job number.

Commit  System generated unique hash for a given commit.

Commit Message  Message that was provided by the application developer when the last code change was committed.

Date  Date.

Owner  Creator of the pipeline with full rights to modify and delete the pipeline. The owner can be changed to another user or team based on access control settings.

Status  Job status. Any issues with the job are shown here.

To view more detailed job information, click any job. The Pipeline Designer appears with a diagram of the entire pipeline. Click a step in the diagram to view details about the corresponding job (or jobs).