Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Configure Git credentials

3 minute read

Set up a Git global configuration for use in CloudBees workflows. The configure-git-global-credentials action authenticates the current user, scoped by default to repositories in the same organization as the workflow repository. After this step runs, all steps using the Git CLI in the same job authenticate with these credentials.

Use this action to avoid failures caused by missing pre-authentication of private repositories. For example, if building a Go module that depends on other private modules, private repository authentication must be in place for go mod download to run successfully.

This action may set up authentication for different types of Git global configurations, including:

CloudBees recommends ensuring that any Git client other than the official Git CLI supports the authentication configuration applied by this action.

Configure access to specific repositories

Use this method to onboard specific repositories by creating an integration in CloudBees Unify.

The following example configures access to multiple repositories using a line-break-separated list:

      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: |
            https://github.com/user1/repo
            https://github.com/user2/rep1
▼

To configure access for all repositories within a GitHub project or user namespace, specify the project URL:

      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: https://github.com/org/
▼

To grant access to all accessible repositories on a host, specify a host URL. Access is determined by the SCM integration and credentials configured in CloudBees Unify for the component and its parent organizations:

      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: https://github.beescloud.com/
▼

Configure access for Bitbucket repositories using a workspace access token

If you have a Bitbucket Workspace access token configured in your SCM integration, grant access to all repositories in a workspace by specifying the workspace URL:

      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: https://bitbucket.org/my-workspace/
▼

Alternatively, specify individual Bitbucket repositories:

      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: |
            https://bitbucket.org/my-workspace/repo-one
            https://bitbucket.org/my-workspace/repo-two
▼

For more information about Bitbucket token types and required scopes, refer to Bitbucket access tokens reference.

Configure access using SSH

Add the SSH key as a secret property in CloudBees Unify and use the SSH clone URL in the repositories input.

When defining the SSH key secret, ensure the secret value ends with a new line. 
      - name: Git global credentials
        uses: cloudbees-io/configure-git-global-credentials@v2
        with:
          repositories: "ssh://github.com/user/repo"
          ssh-key: ${{secrets.<ssh-secret-name-placeholder>}}
▼

Inputs

Table 1. Input details
Input name Data type Required? Description

repositories

String

Yes

Repository clone URL, for example https://github.com/user/repo.

For multiple repositories, CloudBees recommends using a line-break separator, although the parameter also accepts a whitespace- or comma-separated list.

ssh-key

String

No

SSH key used to fetch the repository. Only relevant when an SSH clone URL is provided in the repositories input. In all other cases, the action uses the pre-configured credentials set up in CloudBees Unify for the specified repositories.

ssh-known-hosts

String

No

A list of known SSH hosts to add to the global host database. Use the ssh-keyscan utility to get public SSH keys for a host.

The public keys for GitHub and Bitbucket are added by default.

ssh-strict

Boolean

No

Default is true. When true, performs strict host key checking by adding the options StrictHostKeyChecking=yes and CheckHostIP=no to the SSH command line. Use the ssh-known-hosts input to configure additional hosts.

Related pages

Configure container registry credentials
Integrate external secret providers