> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/pipeline/overview-of-pipelines.md). # Overview of Pipelines {% hint style="warning" %} #### Written for the Old UI This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article. {% endhint %} ## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview Pipelines in Flosum allow you to automate the process of moving changes between environments. A pipeline connects a branch to one or more organizations and defines the steps for validation, testing, and deployment. The Pipelines page provides a searchable list of all available pipelines along with their metadata, making it easy to track activity and manage automation.
{% hint style="info" %} #### Best Practices * **Name pipelines by purpose** (e.g., Release-Branch-Pipeline, QA Team Pipeline). * **Connect only required orgs** to reduce unnecessary runs. * **Use branches strategically** – tie pipelines to stable integration or release branches. * **Review activity logs** regularly to track deployment health. * **Run pipelines after PR approvals** to ensure code quality and conflict resolution before promotion. {% endhint %} ## Pipelines Page When viewing the **Pipelines** page, the following details are displayed:
Pipeline NameThe name assigned to the pipeline.
Created ByThe user who created the pipeline.
Last ActivityThe time since the last execution or update of the pipeline.
BranchSpecifies the branch that triggers the pipeline automatically. If Automatic Launch is off, this field will be blank.
OrganizationsThe number of different organizations assigned to steps in the pipeline.
Actions (⋮)Pipeline options: Edit pipeline name and Delete.
### Searching, Sorting, and Filtering The Pipelines page can be searched, filtered, and sorted: * **Search** – Find pipelines by name. * **Branches** – Filter by associated branches. * **Latest Activity** – Sort pipelines by: * Sort by name A–Z – alphabetical order. * Sort by name Z–A – reverse alphabetical order. * Latest activity – most recent updates first. * Oldest activity – oldest updates first. ## Pipeline Actions The following pipeline actions are all accessible from the Pipelines page: 1. Click **Pipelines** from the left sidebar menu.
{% stepper %} {% step %} ### Creating a Pipeline 1. Click **Create pipeline**.
2. Enter a name for the pipeline in the **Pipeline name** textbox. 3. Click **Create pipeline**.
{% hint style="info" %} Once a pipeline is created, you can configure it by adding steps. See the following article for more instructions. * [Adding a Pipeline Step](/devops/pipeline/configuring-pipeline-steps/adding-a-pipeline-step.md) {% endhint %} {% endstep %} {% step %} ### Running a Pipeline 1. Click **Run pipeline**.
2. Click the **Branch** dropdown menu. 3. Select the branch to run the pipeline from.
4. Click the **Pipeline** dropdown menu. 5. Select the pipeline to run.
6. Click **Run**.
7. After clicking **Run**, the pipeline job starts, and a **Pipeline ran successfully** message is displayed.
{% hint style="warning" %} The **Pipeline ran successfully** message only means that the pipeline job was successfully started. This message does not indicate that the pipeline completed all of its operations successfully. To view the pipeline results, check the branch's activity. {% endhint %} {% hint style="info" %} #### Pipeline Results Viewing a pipeline's progress and results is done from the branch on which the pipeline was run. See the following article for instructions on viewing a pipeline's results. * [Viewing Pipeline Results](/devops/pipeline/pipeline-actions/viewing-pipeline-results.md) {% endhint %} {% endstep %} {% step %} ### Deleting a Pipeline {% hint style="warning" %} #### Warning Make sure the pipeline is no longer required before deleting it, as this action cannot be undone. {% endhint %} {% hint style="info" %} A pipeline can also be deleted when in the pipeline editor, by selecting **Delete** in the upper-right menu. {% endhint %} 1. Click the **Three Dot** menu for the pipeline to delete. 2. Click **Delete**.
3. Click **Yes** in the Delete Pipeline confirmation dialog box.
{% endstep %} {% endstepper %} ## Pipeline Editor When you click a pipeline, the pipeline editor opens. This tool lets you set up the steps in your pipeline and configure Automatic Launch options. For further details on pipeline configuration, refer to these articles. * [Adding a Pipeline Step](/devops/pipeline/configuring-pipeline-steps/adding-a-pipeline-step.md) * [Editing a Pipeline Step](/devops/pipeline/configuring-pipeline-steps/editing-a-pipeline-step.md)
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/devops/pipeline/overview-of-pipelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.