All Collections
Feature guides
Version control
Team-shared source control connections
Team-shared source control connections

What is a team-shared source control connection/VCS? How do I connect one to my Gearset account?

Quinn Kuiper avatar
Written by Quinn Kuiper
Updated over a week ago

What is a team-shared source control connection used for?

Within Gearset the team-shared source control connections are only used in a team-shared continuous integration job or team-shared pipeline.

These connections are managed by the team owners on each Gearset team.

What account should I use for a team-shared connection?

We recommend a service account for the team-shared connection, as all CI jobs and jobs within a team-shared pipeline will be done under this account.

How do I add a team-shared connection to Gearset?

You can add a team-shared connection in the same way as you add a normal connection. From the Source control and services page scroll down to the team-shared source control and services section and select your source control provider, then follow the on-screen instructions.

For more information on how to connect to each source control provider, please see this selection of articles.

Can I change my team-shared source control connections account?

While theoretically possible, you should not change your source control connections account. This account should not be linked to any individual and therefore should not be changed. Doing this could result in any current team-shared CI jobs being unable to run successfully.

What is a service account?

A service account is used to perform source control actions on behalf of a Continuous Integration system.

A service account is a type of account that is not tied to an individual human user. Service accounts are used when the credentials must be set up and maintained without being impacted by changes in the team. This account is created and managed outside of Gearset in your source control provider.

What is a personal connection?

A personal connection is where the account is linked to a named individual connected to a human user on the team. These are unique for each user on the team.

Did this answer your question?