A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.codecov.io/docs/set-up-oauth-login below:

Set Up Oauth Login (Self-Hosted)

A service provider is the product you use to host your source code. Codecov integrates with GitHub, Github Enterprise, Bitbucket, Bitbucket Server (formally Stash), GitLab and GitLab Enterprise.

Please choose one or more provider to link with your Codecov Enterprise via Oauth login. This step is mandatory for setup.

🚧

Do not indent your service provider configuration

A common configuration error is to indent the service provider configuration under the setup block in your codecov.yml. This will result in errors when running codecov enterprise.

When adding service providers, be sure to add them to the codecov.yml as follows:

setup:
    # various setup configs
github_enterprise:
    # provider config
📘

Are you using Github.com or Github Enterprise?

In addition to setting up the Oauth login below (which is mandatory), it is strongly recommended to use the Github App Integration for Codecov Self-Hosted

Below is the guide to link Github.com to your Codecov Self-Hosted.

  1. Follow our GitHub App Integration Install Guide

Append the information collected in step 1 in your self-hosted codecov.yml.

github:
  client_id: "Client ID"
  client_secret: "Client Secret"

Restart your Codecov Self-Hosted to complete the integration.

Your Github Enterprise (GHE) is a self-hosted instance of Github. It likely located behind your firewall. Codecov Self-Hosted will need to communicate with your GHE to function properly. Please follow these configuration steps to setup your instance properly.

Please replace https://enterprise-hostname.com with the root url of your GHE.

  1. Follow our GitHub App Integration Install Guide

Append the information collected in step 1 in your enterprise codecov.yml.

github_enterprise:
  url: "https://github-enterprise-hostname.com"
  api_url: "https://github-enterprise-hostname.com/api/v3"
  client_id: "Client ID"
  client_secret: "Client Secret"

Restart your Codecov Self-Hosted instance to complete the integration.

Below is the guide to link Bitbucket.org to your Codecov Self-Hosted Instance.

  1. Create a new OAuth consumer
  1. Fill in an Application Name, ex Codecov Self-Hosted
  2. Fill in an Callback URL to http://codecov.domain.com/login/bitbucket
  3. Fill in an URL to http://codecov.domain.com/bb
  4. Toggle the permissions as seen in the image below.
  5. Click Save
  6. In your list of OAuth Consumers click on your new entry.

In addition, this box must be checked in order for BitBucket to share the credentials back to Codecov.

Append the information collected in step 1 in your enterprise codecov.yml.

bitbucket:
  client_id: "key"
  client_secret: "secret"

Restart your Codecov Self-Hosted instance to complete the integration.

Bitbucket Server (BBS, formerly Stash) is a self-hosted instance of Bitbucket. Codecov Self-Hosted will need to communicate with your BBS to function properly. Please follow these configuration steps to setup your instance properly.

  1. Create a unique Consumer Key, ex UUID: a49d1f9e-294c-4cd6-a44c-e5e4440e67c9
  2. Configure Application Link at <BBS>/plugins/servlet/applinks/listApplicationLinks
  3. Enter the URL of your Codecov Self-Hosted instance (<CCE>) next to Create a new link button
  4. Fill in application details
  1. Click *Continue
  2. Now the link is added. Please click Edit on the Codecov link.
  3. Click on the tab Incoming Authorization
  4. Fill in the details:
  1. Click Save

    You should now see Codecov in your Application Links

MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9d2iMTFiXglyvHmp5ExoNK2X8nxJ+1mlxgWOyTUpTrOKRiDUbZoZID3TP8CobQ5BsqDOSawHyi+Waf9Ca+iYoTu1fa8yZUreQXAdaK1u61Mn2XCkmITE/N5kvbYjDEWA1Dwb6CsvVkYZXo/Eq1X/3yrLXWKDNEnm0Cq48PFWqMQIDAQAB

Append the information collected in step 1 in your self-hosted codecov.yml.

bitbucket_server:
  url: "<BBS>"
  client_id: "Consumer Key from above"

Restart your Codecov Self-Hosted container to complete the integration.

GitLab.com follows the same install setup as GitLab CE/EE below.

Your Gitlab Enterprise (CE/EE) (aka GLE) is a self-hosted instance of Gitlab. It's likely located behind your firewall. Codecov Self-Hosted will need to communicate with your GLE to function properly. Please follow these configuration steps to setup your instance properly.

Please replace https://enterprise-hostname.com with the root url of your GLE.

📘

Using GitLab.com?

If you're using gitlab.com's hosted offering, you should use https://gitlab.com as your root url.

  1. Create a new application at https://enterprise-hostname.com/profile/applications
  2. Fill in an Application Name, ex Codecov Self-Hosted
  3. Specify the redirect URI for your CE endpoint https://codecov-enterprise-hostname.com/login/gitlab_enterprise
  4. Select all scopes except sudo
  5. Click Submit

Append the information collected in step 1 in your self-hosted codecov.yml.

gitlab_enterprise:
  url: "https://enterprise-hostname.com"
  client_id: "Application Id"
  client_secret: "Secret"

Restart your Codecov Self-Hosted container to complete the integration.

Have a self-signed SSL certificate? Add your ssl.pem with this documentation.

Two steps: (1) add the ssl pem location to your codecov.yml, (2) include it in your docker run

gitlab_enterprise:
  ssl_pem: "/gle.ssl.pem"
docker run -it --rm \
  -v "$PWD/codecov.yml:/codecov.yml" \
  -v "$PWD/gle.ssl.pem:/gle.ssl.pem" \  # this is added
  --link codecov-redis:redis \
  --link codecov-postgres:postgres \
  codecov/enterprise:v?.?.?

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4