This document provides a summary of the Pipelines page in the CircleCI app and documents some of the changes to the CircleCI user interface.
You may have noticed some changes to CircleCI’s web interface lately. We have some exciting changes that are rolling out regarding how your builds are being grouped and the user interface that presents that information. Let’s begin by stating what a Pipeline is.
Pipelines represent the entire configuration that is run when you trigger work on your projects that use CircleCI. The entirety of a
.circleci/config.yml file is executed by a pipeline.
When visiting your CircleCI dashboard you will be presented with the recent pipelines that have run in your organization/account.
Jobs, tests, artifacts
A pipeline is composed of workflows, which are composed of jobs. By navigating from a pipeline to a specific job, you can access your job output, test results and artifacts through several tabs.
Further, the output of each job can be openened in a new tab (in either raw or formatted styling) with a unique link, making it share-able between team members.
Help make this document better
This guide, as well as the rest of our docs, are open-source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guide first).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.