-title:Integrations

url:"/integrations"

pages:

-title:Gitproviders

-title:GitProviders

url:"/git-providers"

-title:Kubernetes

url:"/kubernetes"

title:"Gitproviders"

title:"GitProviders"

description:"Easily checkout code in your pipelines"

group:integrations

redirect_from:

You can add repositories from the other git providers regardless of the one that you used for sign-up. For example, you can use GitLab to sign up with Codefresh, but still build repositories that exist in Bitbucket.

You can even add multiple accounts from each Git provider (if you have more than one) allowing you to use Codefresh as a central CI/CD solution that can access all yourgit repositories regardless of the backinggit provider.

You can even add multiple accounts from each Git provider (if you have more than one) allowing you to use Codefresh as a central CI/CD solution that can access all yourGit repositories regardless of the backingGit provider.

Currently Codefresh supports:

* Atlassian Stash (old version of Bibucket Server)

* Bitbucket Server (new version of Stash)

Atlassian Stash/Bitbucket server as well as the on-premises version ofGiTlab and GitHub are only available to Codefresh enterprise customers.

Atlassian Stash/Bitbucket server as well as the on-premises version ofGitLab and GitHub are only available to Codefresh enterprise customers.

By default, you have direct access togit repositories that exist in theGIT provider that you used while signing up for Codefresh. You can easily create Codefresh projects that checkout code from thatGIT provider without any extra configurations.

By default, you have direct access toGit repositories that exist in theGit provider that you used while signing up for Codefresh. You can easily create Codefresh projects that checkout code from thatGit provider without any extra configurations.

To add additionalGIT providers, go to your Account Configuration, by clicking on*Account Settings* on the left sidebar. On the first section called*Integrations* click the*Configure* button next to*Git providers*.

To add additionalGit providers, go to your Account Configuration, by clicking on*Account Settings* on the left sidebar. On the first section called*Integrations* click the*Configure* button next to*Git providers*.

{% include image.html lightbox="true" file="/images/integrations/codefresh-integrations.png" url="/images/integrations/codefresh-integrations.png" alt="Codefresh Account Integration" max-width="80%" %}

You can add a newgit provider using the*Add Git provider* drop-down.

You can add a newGit provider using the*Add Git provider* drop-down.

{% include image.html

lightbox="true"

file="/images/integrations/git/git-provider-menu.png"

url="/images/integrations/git/git-provider-menu.png"

max-width="60%"

caption="AddGIT provider"

alt="AddGIT provider"

caption="AddGit provider"

alt="AddGit provider"

%}

For eachgit provider you need to setup authentication, so Codefresh can get access to the public and private repositories of the respective platform.

For eachGit provider you need to setup authentication, so Codefresh can get access to the public and private repositories of the respective platform.

The easiest way to setup authentication is with OAuth2 if supported by thegit provider. You only need to name your integration

The easiest way to setup authentication is with OAuth2 if supported by theGit provider. You only need to name your integration

and Codefresh will automatically set it up once you accept the permissions required. If you have problems with OAuth2

or the provider does not support it, you need to manually create credentials by yourself in your git account and then enter them into Codefresh.

For the**Access Token** method you need

* A friendly name for thegit context (it can be anything you want)

* A friendly name for theGit context (it can be anything you want)

* An access token

For more information see the[GitHub Documentation page](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/){:target="_blank"}

The "token description" you enter in your GitHub account in order to create the token is completely arbitrary (use "Codefresh" for an example). Once you have the token, paste it in the Codefresh UI and click*Test connection*. If everything is OK, you can

now save thegit integration.

now save theGit integration.

The minimum permissions for the token are:

For GitHub on-premises you also need to provide the URL of the GitHub server in your organization. If enabled in your account you can setup[Pipeline definition restrictions]({{site.baseurl}}/docs/administration/access-control/#pipeline-definition-restrictions) by expanding the*YAML Options* segment.

If your GitHub installation is behind your firewall, you can also

use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by entering a secrets value

with the same syntax[shown in pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/secrets-store/).

For example if you already have a`token` on a resource call`git-credentials` you can put in the token field the expression {% raw %}`${{secrets.git-credentials.token}}`{% endraw %}.

When the admin clicks off "Allow access to all users" another toggle appears; “Allow these credentials to be shared within a pipeline for cloning a repository“

1. When its turned on, the user that runs a pipeline will be able to clone the repo.

2. When its turned off, the user that runs a pipeline cannot use this integration.

In both cases, the user cannot decrypt the token used in Git integration with CLI or API.

For the required fields use:

***Installation id** - found in step 5

***Appid** - found in step 3

***AppID** - found in step 3

***Private key** - the contents of the file your created in step 3 (but convert it to base64 first)

Click*Test connection* to verify your integration and apply your changes with the*Save* button. If enabled in your account you can setup[Pipeline definition restrictions]({{site.baseurl}}/docs/administration/access-control/#pipeline-definition-restrictions) by expanding the*YAML Options* segment.

For the**Access Key** method you need:

* A friendly name for thegit context (it can be anything you want.)

* A friendly name for theGit context (it can be anything you want.)

* An access token/key

The name you enter in order to create the token in the GitLab UI is completely arbitrary (use "Codefresh" for an example)

Once you have the token, paste it in the Codefresh UI and click*Test connection*. If everything is OK can

now save thegit integration.

now save theGit integration.

For GitLab on-premises you also need to provide the URL of the GitLab server in your organization. If enabled in your account you can setup[Pipeline definition restrictions]({{site.baseurl}}/docs/administration/access-control/#pipeline-definition-restrictions) by expanding the*YAML Options* segment.

For the**Application Password** method you need:

* A friendly name for thegit context (It can be anything you want.)

* A friendly name for theGit context (It can be anything you want.)

* The name of your Bitbucket account/email address

* A Bitbucket application password

%}

The "label" you enter in your Bitbucket account in order to create the application password is completely arbitrary (use "Codefresh" for an example). Once you have the token, paste it in the Codefresh UI and click*Test connection*. If everything is OK you can

now save thegit integration.

now save theGit integration.

If enabled in your account you can setup[Pipeline definition restrictions]({{site.baseurl}}/docs/administration/access-control/#pipeline-definition-restrictions) by expanding the*YAML Options* segment.

Select an expiration date for your token

time period and make sure that you have a policy in place for renewing your tokens so that Codefresh can continue to read yourGIT repo.

time period and make sure that you have a policy in place for renewing your tokens so that Codefresh can continue to read yourGit repo.

{% include image.html

lightbox="true"

For example if you already have a`token` on a resource call`git-credentials` you can put in the token field the expression {% raw %}`${{secrets.git-credentials@token}}`{% endraw %}.

Once your provider is active, you can add a new project into Codefresh and then during the[repository selection screen]({{site.baseurl}}/docs/getting-started/create-a-basic-pipeline/) you will have access to the additionalgit providers.

Once your provider is active, you can add a new project into Codefresh and then during the[repository selection screen]({{site.baseurl}}/docs/getting-started/create-a-basic-pipeline/) you will have access to the additionalGit providers.

{% include image.html

lightbox="true"

file="/images/integrations/git/select-git.png"

url="/images/integrations/git/select-git.png"

max-width="60%"

caption="SelectGIT provider"

alt="SelectGIT provider"

caption="SelectGit provider"

alt="SelectGit provider"

%}

triggering pipelines when a commit (or another event) happens.

After adding the repository Codefresh will behave exactly the same, regardless of the selectedgit provider.

You will be able to[create pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/) for differentgit providers in exactly the same manner.

After adding the repository Codefresh will behave exactly the same, regardless of the selectedGit provider.

You will be able to[create pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/) for differentGit providers in exactly the same manner.