License requirements to use team-shared CI jobs:
This feature is available for all customers using Deployment Teams and Automation Starter licenses, or any license above (e.g. Deployment/Automation Enterprise license).
Check our Pricing page for more information about different types of licenses.
On larger teams, with members potentially joining and leaving on a regular basis, it can cause administrative overhead to maintain CI jobs if they are set up by individual team members.
In this case, team owners can instead create connections that are owned by all team owners rather than any individual.
Adding a team-shared CI job
Prerequisites: team-shared org and VCS connection
Before you create a team-shared CI job, it is required for you to use team-shared org and team-shared VCS (Version Control System) connections - if you don't have them configured yet, then you will need to create these first.
Why Gearset recommend using a service account?
When setting up team-shared connections, we suggest using a service account. This is because once a team-shared CI job is created, its credentials cannot be changed — the only way to update them later is to re-create the job entirely.
When a team owner creates a CI job, they can elect to create a team-shared job, rather than a user-owned job.
To do that, on the CI dashboard page select "Add new team-shared deployment job..." (example below).
When you create a team-shared job, the job is owned not by you but by all team owners. This means that it will continue to be available to team members even if you leave your Gearset team in the future.
Permissions
Team-shared CI jobs can be edited and managed by any team owner. While team members can’t edit or manage these jobs, they can still run them under the same rules as user-owned CI jobs. In other words, a team member’s ability to run a team-shared CI job depends on their permissions for the source and target connections.
Use with VCS connections
When team-shared CI jobs use a version control system (VCS) connection, a team-shared VCS connection for that provider must exist. Ideally, using service account credentials.
However, it is highly recommended that users also have their own user-owned connections configured with their own credentials for accurate attribution and auditing.
FAQs
Is it possible to use the same CI job in more than one Gearset Pipeline?
Is it possible to use the same CI job in more than one Gearset Pipeline?
No, this is not possible. A single user-owned or a team-shared CI job can only be used in one Gearset Pipeline.
What's the workaround?
If you want to use the same CI job in multiple Pipelines, you’ll need to create a new CI job with the same source and target environments and identical configuration settings. Once created, you can add this new job to the additional Pipeline.
For this, you can use the "Duplicate job" option which is available on the CI dashboard.
