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 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 recommends to use a service account?
When creating the team-shared connections, we recommend using a service account. It's because later on, there is no way to change credentials of your team-shared CI job, without having to re-create that job.
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. Team members cannot edit or manage the jobs, but they can run the jobs according to the same rules as user-owned CI jobs - in other words, whether a team member can run a team-shared CI job depends on a given member's permissions to the source and target connections.
Use with VCS connections
When team-shared CI jobs use a 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 utilised in one Gearset Pipeline.
What's the workaround?
If you want the same CI job to be used in more than one Pipeline, please create a new CI job with the same source and target environments, along with all other configuration settings. And then add that new job to the Pipeline - this is possible.
For this, you can use the "Duplicate job" option which is available on the CI dashboard.
