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 clicking on the lock icon that appears next to field.

{% include

image.html

lightbox="true"

file="/images/pipeline/secrets/lock-icon.png"

url="/images/pipeline/secrets/lock-icon.png"

alt="Using a connected secret in the Codefresh GUI"

caption="Using a connected secret in the Codefresh GUI"

max-width="50%"

%}

If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.

If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.

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.

If your GitLab 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 clicking on the lock icon that appears next to field.

{% include

image.html

lightbox="true"

file="/images/pipeline/secrets/lock-icon.png"

url="/images/pipeline/secrets/lock-icon.png"

alt="Using a connected secret in the Codefresh GUI"

caption="Using a connected secret in the Codefresh GUI"

max-width="50%"

%}

If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.

If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.

For the**OAuth2 method** you only need to enter a name for your connection and click*Save*. Then accept the permissions dialog. This is the easiest and recommended way to integrate Bitbucket. Notice that if

Codefresh supports Bitbucket server versions 5.4.0+ since those expose the API used by the integration.

If your Bitbucket Server 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 clicking on the lock icon that appears next to field.

{% include

image.html

lightbox="true"

file="/images/pipeline/secrets/lock-icon.png"

url="/images/pipeline/secrets/lock-icon.png"

alt="Using a connected secret in the Codefresh GUI"

caption="Using a connected secret in the Codefresh GUI"

max-width="50%"

%}

If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.

If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.

- Using external secrets in Codefresh GUI -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/secrets-store/#using-secrets-in-the-codefresh-gui)

- Using external secrets in Github, Gitlab and Bitbucket server integration -[documentation]({{site.baseurl}}/docs/integrations/git-providers/#using-external-secrets-for-the-token)

- Using external secrets in shared configuration -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/#using-external-secrets-as-values)

- Using external secrets in cloud storage integration -[documentation]({{site.baseurl}}/docs/testing/test-reports/#connecting-an-s3-bucket)

- Get Code Coverage Reports with Codacy -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/codacy-testing)

- Git clone now supports a proxy connection -[documentation]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/#using-git-behind-a-proxy)

- Support for other container runtimes (containerd, cri-o) in the Runner -[documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#prerequisites)