The connector reads one Codecov organization — the organization identified
by the git service and owner you configure. It syncs that organization’s
members. Each member’s profile carries whether they are an admin of the
organization and whether they hold a seat (are activated). Members who hold
a seat sync as enabled users; members on the roster without a seat sync as
disabled, which is useful for offboarding review.
To read the full member roster, the API token must belong to an admin of
the organization you are syncing. A non-admin token sees only a partial
roster.
1
Sign in to Codecov as an admin of the organization you want to sync.
2
Open Settings > Access and create a new API token. Copy the
token value.
3
Note the git service that hosts the organization — one of GitHub,
GitLab, Bitbucket, GitHub Enterprise, GitLab Enterprise, or Bitbucket
Server.
4
Note the organization’s owner slug on that git service. For a GitHub
organization this is the organization login.
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Codecov and click Add.
3
Choose how to set up the new Codecov connector.
4
Set the owner for this connector.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the Codecov credentials:
Codecov API token: the API token you created, belonging to an
admin of the organization.
Git service: the git service hosting the organization — one of
github, gitlab, bitbucket, github_enterprise,
gitlab_enterprise, or bitbucket_server.
Organization: the organization’s owner slug on that git
service.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Codecov connector is now pulling access data into C1.
Follow these instructions to run the Codecov connector in your own
environment.
1
Create a secret for the Codecov API token.
2
Configure the connector environment variables:
BATON_CODECOV_API_TOKEN: the API token belonging to an admin
of the organization.
BATON_CODECOV_SERVICE: the git service hosting the
organization — one of github, gitlab, bitbucket,
github_enterprise, gitlab_enterprise, or bitbucket_server.
BATON_CODECOV_OWNER: the organization’s owner slug on that git
service.
3
Deploy the connector using your standard self-hosted connector process.
Done. Your Codecov connector is now pulling access data into C1.
