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

Set up GitHub Actions integration

1 minute read
On this page

Integrate GitHub Actions (GHA) with CloudBees Unify so that your GHA workflows and runs are visible in the CloudBees Unify UI. For background on how the integration works, refer to Understanding GitHub Actions integration.

To set up the integration:

  1. Install the CloudBees GitHub App. For details, refer to GitHub integrations.

    On occasion, new features in CloudBees Unify may require updates to permissions in the GitHub App for full functionality. Verify that the following permissions are set in the CloudBees GitHub App installation:
    Table 1. Installed GitHub App required permissions
    Read access Write access Key

    Actions

    Commit statuses

    Contents

    Metadata

    Events

    Pull requests

    Webhooks

  2. Create a GHA workflow in the GitHub repository connected to CloudBees Unify, or confirm that an existing GHA workflow is in the connected repository.

    Observe the following constraints when authoring or reviewing your GHA workflow:

    • Do not include a forward slash with spaces on both sides (` / ) in a job name, for example `build / reusable-job / test. GHA reports job statuses for reusable workflows using this pattern to represent hierarchy. CloudBees Unify interprets any forward slash with spaces on both sides as indicating a reusable workflow job and does not correctly display Run details for that job.

  3. Create a component connected to the repository that contains your GHA workflow.

    Only GHA runs that occur after successful integration with CloudBees Unify are displayed.

Related pages

Understanding GitHub Actions integration
Display GitHub Actions workflows and runs