> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-versions-and-deployments.md).
# Pipeline versions & deployments
## Introduction
Each time a pipeline is saved, a new version is created, and the previous version is stored. Using the [deployments option](#user-content-fn-1)[^1] (from the editor) to access the *Versions & Deployments* page, you can [preview & compare](#previewing-and-comparing-a-previous-pipeline-version), [deploy](#deploying-a-pipeline), or [restore](#rolling-back-to-a-previous-pipeline-version) available versions. For example:
## Pipeline versions
You'll find the five most recent versions in the lower section of the [*Versions & Deployments*](#introduction) page - for example:
### Working with pipeline versions
Previewing & comparing a previous pipeline version
When you're working with a pipeline in the editor, it can sometimes be useful to check the setup for a previous version and/or to compare it with your current setup. You can do this with the `preview` option.
{% stepper %}
{% step %}
**Access deployments for the pipeline**
Click the `deployments` button from the editor. For example:
{% endstep %}
{% step %}
**Preview the required version**
Find the version that you want to review, then click the `preview` button. For example:
{% endstep %}
{% step %}
**Work with the preview**
The editor splits into two panels with your current (editable) version on the left and the (read-only) preview version on the right . For example:
The left (current version) panel works as normal - you can add, edit, or remove nodes as needed. You can't make changes in the right (preview) panel, but you can:
* Zoom in and out to adjust the view.
* Click any node to view settings.
* Use the `full screen` button to hide the current version and view the preview in full screen mode (then click `split screen` to return to both panels).
{% endstep %}
{% endstepper %}
Deploying a pipeline version
You can deploy any version of a pipeline to any environment, but only one version of the same pipeline can exist in a given environment. If you deploy a pipeline version to an environment where another version already exists, the existing version is overwritten.
When a pipeline version is deployed, it is [enabled](#enabling-and-disabling-a-pipeline-deployment) automatically. This means the pipeline runs automatically, according to defined [trigger](/documentation/brigge-for-transformers/pipelines/pipeline-nodes/trigger-node.md) settings.
To deploy a pipeline:
{% stepper %}
{% step %}
**Access deployments for the pipeline**
Click the `deployments` button from the editor. For example:
{% endstep %}
{% step %}
**Deploy the required version**
Find the version that you want to deploy, then click the associated `deploy` button. For example:
{% endstep %}
{% step %}
**Choose an environment**
Select the required environment. For example:
{% endstep %}
{% step %}
**Confirm the deployment**
Click save to confirm this deployment to the selected environment. For example:
{% endstep %}
{% endstepper %}
Restoring a previous pipeline version
Restoring a previous pipeline version restores the pipeline structure from that point in time to the editor. It does NOT affect the currently deployed version.
Having restored an older version, you can make changes and (if required) deploy this updated version. To restore a pipeline version to the editor, follow the steps below:
{% stepper %}
{% step %}
**Access deployments for the pipeline**
Click the `deployments` button from the editor. For example:
{% endstep %}
{% step %}
**Deploy the required version**
Find the version that you want to restore, then click the associated `restore` button. For example:
{% endstep %}
{% step %}
**Confirm this action**
If you're sure that you want to restore this version to the editor, confirm this action when prompted. For example:
{% endstep %}
{% endstepper %}
## Pipeline deployments
A pipeline can be deployed once to any given [environment](/documentation/brigge-for-transformers/environments.md). So, if you have multiple environments, you'll likely have multiple deployments for any given pipeline. When a pipeline is [deployed](#deploying-a-pipeline), that deployment is [enabled](#enabling-and-disabling-a-pipeline-deployment). This means the pipeline runs automatically (in the associated environment), according to defined [trigger](/documentation/brigge-for-transformers/pipelines/pipeline-nodes/trigger-node.md) settings.
Existing pipeline deployments are displayed in the top section of the [*Versions & Deployments*](#introduction) page. For example:
### Working with pipeline deployments
Viewing deployment details
Click any deployment to view more deployment details, including the deployed version number and defined triggers. For example:
{% hint style="info" %}
This is where you'll find [webhook](/documentation/brigge-for-transformers/pipelines/pipeline-nodes/trigger-node.md#webhook-triggers) and [file upload](/documentation/brigge-for-transformers/pipelines/pipeline-nodes/trigger-node.md#file-upload-triggers) URLs for triggers, for use in your external systems.
{% endhint %}
Enabling & disabling a pipeline deployment
If you need to stop a pipeline running on its automatic trigger(s), for example, if you are troubleshooting an issue, you can disable the deployment for the required environments. Then, when you're ready, you can enable the deployment again (or deploy another version).
To do this, use the toggle option associated with the required deployment - for example:
{% hint style="info" %}
You can also view deployment details from the [pipelines list](/documentation/brigge-for-transformers/pipelines/the-pipeline-list.md).
{% endhint %}
[^1]: **How do I get there?**\
Select the 'cog' icon from the canvas:
