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

Understanding GitHub Actions integration

2 minute read

The GitHub Actions (GHA) integration connects GHA workflows to CloudBees Unify, giving teams CloudBees analytics and security dashboards without requiring migration away from GHA. The integration works in two directions: CloudBees Unify displays GHA workflow activity, and GHA actions push data back into CloudBees Unify.

What the integration provides

The integration provides visibility and data publishing.

Visibility. GHA workflows, runs, and jobs are displayed in the CloudBees Unify UI. Within the run details view, you can see test results, build artifacts, evidence items, and deployment information generated by GHA, the same data available for CloudBees-native workflows.

Data publishing. Dedicated GHA actions let workflows push data into CloudBees Unify:

  • Register build artifacts and manage artifact version labels.

  • Publish test results from JUnit, TestNG, and other test frameworks.

  • Publish evidence items for audit and traceability.

  • Publish security scan findings from tools such as Black Duck, Coverity, Gitleaks, Gosec, Grype, Trivy, and Klocwork.

  • Trigger CloudBees workflows from a GHA run.

How the integration works

The CloudBees GitHub App acts as the bridge between GitHub and CloudBees Unify, establishing the webhook connection that allows CloudBees Unify to receive GHA workflow events. A CloudBees Unify component must be connected to the repository containing the GHA workflow for events to be received and displayed.

Only runs executed after successful integration are displayed. Historical runs are not back-filled. If you connect an existing GHA workflow, only runs that occur after the integration is in place appear in CloudBees Unify.

GitHub Actions integration vs CloudBees workflows

The GHA integration and CloudBees-native workflows serve different starting points.

The GHA integration is designed for teams already invested in GHA who want CloudBees visibility, analytics, and security posture data without migrating their existing automation. GHA continues to execute the workflows; CloudBees Unify observes and enriches the results.

CloudBees-native workflows are designed for teams building new automation or ready to migrate fully to the CloudBees platform. They run directly on the CloudBees workflow engine and have access to the full suite of CloudBees actions.

Both approaches can coexist within an organisation. A team can retain GHA for existing workflows while building new workflows natively in CloudBees Unify.

Related pages

Set up GitHub Actions integration