All Collections
Gearset Pipelines
Getting Started
An introduction to Gearset Pipelines
An introduction to Gearset Pipelines

Use Gearset Pipelines to visualize and control your release process from start to finish

Oli Lane avatar
Written by Oli Lane
Updated over a week ago

Based on Gearset's powerful CI jobs, Pipelines brings some new functionality to help you manage where changes are in your release process, and helps give your entire team visibility and control over the workflow.


Pipelines is available now and we are constantly working to improve it. We have lots of plans for what we'd like to add soon, but this is a broad summary of what's available right now:

  • Visualization: Get an overview of your entire release pipeline, with quick visibility of where your changes are in your release process, what needs to happen to move them forwards, and how much work you have in flight.

  • In-app merging: Promote changes by merging branches from within Gearset, using a new merge algorithm we've devised. This algorithm is specifically designed to make metadata merge conflicts much less likely, plus we run an additional validation to ensure the deployment is successful.

  • Propagating changes: Automatically make merged changes available for promotion to other environments in the release pipeline. Forward-propagate changes downstream through to release, and back-propagate changes into upstream environments that don't currently contain them.

  • Tight source control integration: Whether you're working within Gearset or in your version control system, see the same changes and status, allowing your entire team to work together seamlessly.

  • JIRA integration: Automatically update associated JIRA tickets when a work item gets into each successive environment in your pipeline.

This is just a high-level overview. For more information, see the other articles in this section, where we walk through each of these points in more detail.

Getting started with Gearset Pipelines

What you'll need:

  • A hosted repository containing your Salesforce metadata, or the ability to set this up. Gearset Pipelines is compatible with the following git providers:

    • Azure DevOps

    • Azure DevOps Server

    • AWS Code Commit

    • Bitbucket

    • Bitbucket Server

    • GitLab

    • GitLab self-managed

    • GitHub

    • GitHub Enterprise

  • To be comfortable using the branching model supported by Gearset Pipelines.

  • An Automation Platform license to access the Pipelines feature. The feature is also available during the 30-day free trial of the Gearset application.

Now you’re familiar with why you’d want to use Gearset Pipelines, the next document will look at the supported branching model.

Did this answer your question?