OpsMx
Ask or search…
K
Links

Pipeline Execution

The pipeline execution tab contains a list of all pipeline executions and contains a summary of the following:
  • Pipeline Runs
  • Successful Runs
  • Failed Runs
  • Cancelled Runs
To see the pipeline execution page click Audit from the application dashboard and the pipeline execution screen appears as shown in the image below:
You can resize the width of any columns as per you need to adjust the view . On hovering over the columns a double arrow appears, adjust the arrow to resize the column width.
In the above image, the list of pipelines is displayed and has the following details:
  • CD Name - The name of the Spinnaker Instance
  • Application – This column shows the application
  • Service – This column shows the name of the service
  • Pipeline - This column shows the pipeline of the application
  • Status - This column shows the status of the deployment
  • Execution Data - This column shows the particular pipeline execution data
  • Integrations Data - This column shows the pipeline custom stages
  • Pipeline Duration - This column shows the execution time of the pipeline
  • Stage Duration - This column displays a graph of the stage execution time duration
  • Start Time - This column shows the deployment start time
  • End Time - This column shows the deployment end time
  • Triggered By - This column shows the user who triggered the deployment
  • Cluster - This column shows the name of the cluster.
  • Account - This column shows the application configured account
  • Cloud Provider - This column shows the application configured the account of cloud provider
  • Build Number - This column shows the build number
  • Execution Id - This column shows the application execution ID
  • Server Group - This column shows the application configured server group
  • Judgement Time - This column shows the Judgement Time
  • Judged By - This column shows the name of the user who executed the pipeline execution. On clicking the link, it displays the list of all the users who executed the pipeline execution.
  • Pipeline Config Id - This column shows the Pipeline Config Id
  • Pipeline Id - This column shows the Pipeline Id
  • Pipeline Run - This column shows the Pipeline status of the link

Execution Data

Users can view the execution data for the specific pipeline by following the steps listed below:
  1. 1.
    Click Audit and click the execution data View button for the specific application as shown below:
2. On clicking the View button, the entire pipeline json will appear, as shown in the image below:

Integrations Data

Users can view custom stages of the pipeline by following the steps listed below:
  1. 1.
    Click Audit and click the Connector Data View button for the specific application as shown below:
2. On clicking the View button, the pipeline custom stages will be displayed, as shown in the image below:

Pipeline Duration

Pipeline Duration shows the execution time of the pipeline. Duration will be calculated based on the start and end time of Pipeline execution. Follow the steps below to see the pipeline duration:
Click Audit and see the Pipeline Duration for the specific pipeline as shown below:

Stage Duration

Stage Duration shows a graph of the stage execution time duration. It displays an application's deployment lead time from code commit to production deployment and the user to identify stages that cause high lead times. Follow the steps below to see the Stage Duration:
  1. 1.
    Click Audit and click the Stage Duration View button for the specific application as shown below:
2. After clicking the View button, a graph of the stage execution time duration will be displayed, as shown in the image below:

Show/Hide Columns

You can opt to show or hide these columns in the list available. To do so, click the menu icon as shown in the image below:
The list of available columns will appear. You can select/deselect a particular column from the drop-down to add/remove it from the pipeline table as shown below:

Show Data For

The Show Data for filter is used to display the pipeline executions based on the selected date range.
The following date ranges are available to filter the executions:
  • Today - The number of executions that were executed today are displayed.
  • Yesterday - The number of executions that were executed yesterday are displayed.
  • Last 7 Days - The number of executions that were executed for the last 7 days are displayed.
  • This Month - The number of executions that were executed for this month till today are displayed.
  • Last 1 Month - The number of executions that were executed for the past one month (last 30 days) till today are displayed.
  • Last 6 Months - The number of executions that were executed for the past 6 months (last 180 days) till today are displayed.
  • All - The entire list of executions that were executed till date are displayed.
  • Custom Range - You can customise the to and from dates for which you want the executions to be displayed.
Let’s take an example where you have around 200 pipelines on the list. However, if you'd like to see the details of a specific pipeline or set of pipelines, you can use this option to simply search for a pipeline by Pipeline name or any Pipeline parameter data or Stage name.

Search Pipeline Name:

For example, If you want to see the “test” pipeline from the list of available pipelines. To do so, enter the pipeline's name into the Search text box, and the list will only display pipelines with that name, as shown in the image below. Before proceeding, double-check the application name.

Search Parameters:

You will be able to search the Execution data by one of the parameters (It must be a key or a value in the json).
For example, If you want to see the pipeline with the end time "1660900755978" from the available pipelines:
  1. 1.
    Enter "1660900755978" into the Search text box, and the list will only show the pipelines that contain the specified end time, as shown in the image below:
2. Click the execution data “View” button and the entire pipeline json will popup as shown in the image below:

Last modified 1mo ago