Team-shared pipelines are owned by Gearset Team Owners, rather than individual users.
This gives greater flexibility to teams to manage their orgs, CI jobs and pipelines.
How to convert a pipeline
Requirements for user-owned Pipelines:
You must be the owner of the Pipeline in order to be able to convert it to a team-shared one. If you're not the Pipeline owner, this option won't be available to you.
To convert a pipeline, go to the pipeline settings (cog icon) on the Pipelines UI page, and select the option to Convert to a team-shared pipeline...
This will provide a list of CI jobs within the pipeline, all of which must be converted into team-shared CI jobs before you can convert the pipeline.
Note: Before a Pipeline can be converted to a team-shared (Pipeline) connection, both all associated CI jobs and Salesforce org connections must first be updated to team-shared connections.
Add team-shared source control connection
First, you will have to ensure that you have a team-shared source control connection added.
A tip on best practices:
Gearset recommends setting up a service account for your team-shared VCS connection.
Once this is established, you should see the following notification in our app:
After the team-shared VCS connection is added in Gearset, you will not have to re-add it again. This setup is only configured once.
Add team-shared org connections
Once the team-shared VCS connection is added, you can move to adding team-shared org connections.
A tip on best practices:
Gearset recommends using a service user Salesforce account for all of the team-shared org connections used in the Gearset Pipeline.
Expected scenario where orgs aren't yet converted to team-shared ones
Expected scenario where orgs aren't yet converted to team-shared ones
When the option to Convert to a team-shared CI job is greyed out, this is usually for one of below reasons:
- Your Salesforce org connection used in that CI job has not been converted to a team-shared org connection.
- Your version control system used in Gearset Pipeline isn't added as a team-shared connection on Source control and services page in our app.
This is when you're expected to see below notification in Pipelines:
"Some of the resources used by this CI job are not team-shared so it cannot be converted yet. Expand this row to see the source and target of the job."
On the Pipelines Migration page, you'll see the option to Create a new team-shared org.
Select this option to convert your existing personal org connection to a team-shared connection.
Note: This action will remove the existing personal org connection visible in My org connections tab on your Salesforce orgs page in the app.
Instead, after conversion, your team-shared org will show up on the Team-shared org connections tab.
Once a team-shared org connection has been added, you are then able to Convert to a team-shared org.
Here is the process for converting an org to a team-shared one:
Keep in mind that the above process will need to be repeated for each org and CI job within your Gearset Pipeline.
Convert to team-shared CI jobs
Once both of the above connections have been added into Gearset, you can proceed to select Convert to a team-shared CI job, as the button should become available to select.
Here is the process for converting to a team-shared CI job:
Once all the CI jobs have been converted to team-shared CI jobs, you're finally able to convert the entire Pipeline to a team-shared pipeline connection.
Add a team-shared Pipeline connection
Note: Converting to a team-shared Pipeline is a permanent change that cannot be undone.
After selecting Convert to a team-shared Pipeline, you'll be asked to confirm that you understand you're making a permanent change to a team-shared Pipeline before proceeding.
Once your pipeline is converted, you will gain all the features of a team-shared pipeline.
Note: Team-shared Pipelines are owned by all the team owners on your Gearset team!
All team-shared pipelines are available on the Pipelines UI page, on the dropdown menu (on the left) under the TEAM-SHARED list.
