DevOps Pipeline UI
Summarize
Summary of DevOps Pipeline UI
The DevOps Pipeline UI in ServiceNow provides a graphical, real-time visualization of pipeline executions, showing step progression, status, and detailed information about commits, artifacts, test results, and quality metrics. It integrates with Azure DevOps to display parallel stages and reflects the live pipeline state as executed in Azure DevOps. This UI enables quick insights into how pipeline stages are connected and performing, accessible directly from DevOps forms or related Change Requests.
Show less
Key Features
- Pipeline Visualization: Displays pipeline steps, including parallel stages, with color-coded status indicators (green for success, yellow for waiting, red for failure, grey for not yet run).
- Change Request Integration: Direct links to associated change requests created by DevOps for each step, enabling users to view and act on related changes.
- Pipeline History and Attempts: Shows the most recent 20 pipeline executions and all rerun attempts for any stage or job, allowing detailed tracking of pipeline retries.
- Artifact and Commit Details: Presents artifact versions, work items, and commits associated with the pipeline. Note that commits reverted within the same execution are excluded from the commit list.
- Test and Quality Results: Displays build test results, including pass percentages and throughput, as well as software quality (e.g., SonarQube scans) and security scan results, all customizable via UI settings.
- Status Updates and Controls: Status buttons require a view reload to refresh, and a system property can be set to enable automatic cancellation of change requests if pipeline steps fail.
- Ordering and Visibility: The order of pipeline cards is determined by the configured sequence in DevOps; skipped stages are not shown.
Practical Use and Benefits
ServiceNow customers can leverage the DevOps Pipeline UI to gain immediate, consolidated visibility into their CI/CD pipelines directly within ServiceNow. This facilitates faster issue identification and resolution by showing real-time pipeline status, detailed execution attempts, and comprehensive test and quality metrics. Integration with Change Management allows seamless tracking of changes alongside pipeline progress, enhancing coordination between development and operational teams.
Customizable views for software quality and security results empower teams to focus on relevant metrics, while artifact and commit details provide traceability. The UI's support for parallel stages and rerun attempts reflects complex pipeline workflows accurately, helping customers monitor and improve their DevOps processes efficiently.
Use the Pipeline UI to visualize interactions and results across a pipeline execution. This graphical view shows pipeline step progression and other details for each pipeline.
From DevOps, get a quick view of how everything is connected to see exactly what is happening with the pipeline and when. From the ServiceNow Change Management application, you can access the Pipeline UI and quickly see the commits, the committers, and other details for the change request in one place.
The Pipeline UI displays parallel stages as modeled in Azure DevOps release pipelines. The pipeline UI displays the real-time state of the pipeline as it appears in Azure DevOps. The associated artifact details sourced from the build pipeline, Test Results, Software Quality Summary Results also display on the pipeline UI. For more information, see Parallel stages in Azure DevOps release pipelines.
The Pipeline UI shows all attempts of any stage or job that has been rerun or restarted. For more information, see Restarting failed build or release pipeline jobs and stages.
The Pipeline UI shows the pipeline steps that ran instead of the steps configured in DevOps.
- DevOps Pipeline form
- DevOps Pipeline Execution form
- Change Request form created by DevOps
| Green | Successful. All step executions associated to the pipeline execution passed. |
| Grey | Not yet run. |
| Yellow | Waiting (pending, building, validating). At least one step execution is waiting. |
| Red | Failed. At least one step execution failed. Task execution end date is populated even when the change is rejected. Note: To enable the canceling of the change request associated with the step when the step
fails, you must set the sn_devops.cancel_change_on_pipeline_cancel
property to Yes. For more information, see Properties installed with DevOps. |
The order the cards appear in the Pipeline UI by task execution.
| UI feature | Description |
|---|---|
| Pipeline steps | Timing.
|
| View change request | Change request record. Click directly into the change request of the step that was created by DevOps to view details of the change and take action. Note:
|
| Pipeline history | Pipeline Execution. Click a history tile to view the previous step details for a pipeline execution. Note: Pipeline history is displayed for only the most recent 20 pipeline executions. |
| View all attempts | All attempts that the job has run in a step. Click the link in the relevant step to view all attempt details. |
| Artifacts |
Note: Commits reverted in the same pipeline execution are not shown in the commit
list. |
| Test Results | View the build test results to see what tests passed or failed. The quality card contains test summaries:
|
| Software Quality Results | View all the software quality (SonarQube scan) results grouped by project name that were fetched as part of the selected pipeline. You can view the scan results for all categories in a pipeline execution step. You can customize the results that are displayed in the Pipeline UI by configuring the columns in the () property in a comma separated format.
|
| Security Results | View all the security results that were retrieved as part of the selected pipeline. You can view the scan results for all categories in a pipeline execution step. You can customize the results that are displayed in the Pipeline UI.
|
Click directly into DevOps change requests, step executions, artifacts, artifact versions, work items, test summaries, and reattempts in flyout windows.