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

Display GitHub Actions workflows and runs

3 minute read

Once you have set up the GitHub Actions integration, view your GHA workflows and runs directly in CloudBees Unify. GHA workflow and run data is available in the Workflows, Runs, run details, and analytics screens.

All GHA workflow and run data is also available in the Component summary. To view, select Components, and then select the component containing the GHA workflow.

View GHA workflows

The component containing the GHA workflow is listed in the components list for your organization.

To view GHA workflows:

  1. Select Components, and then select the component containing the GHA integration to view the component details.

  2. Select Components  Workflows to list all workflows for that component.

In the Workflows listing, all GHA workflows contain the same information as CloudBees Unify workflows, except:

  1. The Provider for all GHA workflows is identified as GitHub.

  2. To edit a GHA workflow, select the workflow file link to access the YAML file in GitHub. Currently, you cannot directly edit a GHA workflow in CloudBees Unify. View the workflow file as read-only by selecting the workflow name.

View GHA runs

To view GHA runs:

  1. After running your GHA workflow in GitHub, select Components in CloudBees Unify.

  2. Select the component containing the GHA workflow, and then select Components  Runs to list all runs.

Only GHA runs that have occurred from your GHA workflow after its successful integration with CloudBees Unify are displayed.

In the Runs summary list, all GHA runs contain the same information as CloudBees Unify workflow runs, except:

  1. All GHA runs include the GHA unique run attempt number, which increments only when a workflow is run using the Rerun option in GitHub.

  2. The GHA workflow link redirects to the workflow YAML file in GitHub.

  3. The Provider for all GHA runs is identified as GitHub.

GHA runs
Figure 1. GHA compared to CloudBees workflow runs.

View GHA run details

All run details available for CloudBees Unify runs are also displayed for GHA runs, except for job logs and deployment data. For more information, refer to Monitor workflow runs.

Refer to Supported trigger types for information about displayed run details.

View job logs

Job information for a GHA workflow run is available in its run details.

To view job logs:

  1. Select Components  Runs  Run details for your selected run.

  2. Select the JOB LOGS tab in Jobs.

Currently, only step summaries are available in CloudBees Unify. Select View logs on GitHub to access detailed job logs on GitHub.

GHA job logs
Figure 2. Highlighted link to view detailed GHA job logs.

View GHA data in analytics dashboards

GHA workflow and run data is displayed on the analytics dashboards for your organization. In all analytics dashboards, the provider (GitHub) is listed where applicable. The following dashboards are only populated once you add specific actions to your GHA workflow:

Software delivery activity

To populate this dashboard, register artifact metadata and deployed artifact metadata from a GHA run. Refer to Publish GHA deployed artifacts.

DORA metrics

To populate this dashboard, register artifact metadata and deployed artifact metadata from a GHA run. Refer to Publish GHA deployed artifacts.

Security insights

To populate this dashboard, report scan results to CloudBees Unify. Refer to Scan with GitHub Actions.

Test insights

To populate this dashboard, publish test results from a GHA run. Refer to Publish GHA test results.

GHA run and implicit scan
Figure 3. Different providers highlighted in Workflow runs.

Supported trigger types

The following trigger types in GHA workflows are fully supported in CloudBees Unify. GitHub supports other trigger types; CloudBees Unify lists runs invoked by those types but may not provide all relevant details.

Table 1. Supported trigger types from GHA workflows
Trigger type DSL syntax

Push

push

Pull request

pull_request

Manual

workflow_dispatch

Scheduled

schedule

Reusable workflow

workflow_call

Related pages

Set up GitHub Actions integration
Register GHA build artifacts