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

Publish GHA deployed artifacts

2 minute read

Register deployed artifact metadata from your GitHub Actions workflow to CloudBees Unify to track artifact deployments across environments. Use deployment data to enable DORA metrics, environment inventory tracking, and deployment analytics for artifacts deployed through GHA workflows.

This action is available on the GitHub Marketplace.

This action uses GitHub OIDC authentication to securely communicate with CloudBees Unify. Be sure to set permissions to id-token: write in your workflow.

For more information about working with artifacts in CloudBees Unify, refer to Manage workflow artifacts.

Inputs

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

cloudbees-url

String

No

URL of the CloudBees Unify API. Defaults to https://api.cloudbees.io.

target-environment

String

Yes

Deployment environment. You must create the environment in CloudBees Unify before using it in this action.

labels

String

No

Comma-separated labels for this deployment.

artifact-id

String

No

ID of the artifact, generated by the register-build-artifact action. Either this or artifact-url must be present.

artifact-url

String

No

URL of the deployed artifact. Either this or artifact-id must be present.

Outputs

This action produces no output.

Usage examples

The following is a basic example of using the action:

    permissions:
      id-token: write
      contents: read
    steps:
      - name: register-deployment-step
        uses: cloudbees-io-gha/register-deployed-artifact@v1
        with:
          target-environment: pre-prod
          labels: v1.0.0, rc1
          artifact-id: 87ace777-ab20-4867-ac3f-ad5c28f46a29
▼

The following example uses the artifact URL instead of the artifact ID:

    permissions:
      id-token: write
      contents: read
    steps:
      - name: register-deployment-step
        uses: cloudbees-io-gha/register-deployed-artifact@v1
        with:
          target-environment: production
          artifact-url: https://hub.docker.com/repository/docker/example
▼

Full workflow and run example

Running this workflow creates an artifact that is reported to CloudBees Unify, and then that artifact is deployed.

Example GHA workflow YAML file
name: GHA Workflow

on:
  - workflow_dispatch

jobs:
  build-deploy:
    runs-on: ubuntu-latest
    permissions:
      id-token: write
      contents: read
    steps:
      - name: Compile Code
        run: echo "Compiling..."

      - name: Produce Binary
        run: echo "Generating binary..."

      - name: Push binary
        run: echo "Pushing Binary to ECR..."

      - name: Register Build Artifacts in CloudBees Unify
        uses: cloudbees-io-gha/register-build-artifact@v3
        id: go-action
        with:
          name: "gha-artifact-step"
          version: 1.0.0
          url: "docker.io/example:latest"
          digest: sha256:1234567890abcdef123456123456abcdef789078907890abcdefabcdef123456
          label: For testing
          type: docker

      - name: Deploy artifact
        run: echo 'Deploying Build ArtifactId ${{ steps.go-action.outputs.cbp_artifact_id }}'

      - name: Register deployment
        uses: cloudbees-io-gha/register-deployed-artifact@v1
        with:
          target-environment: pre-prod
          labels: For testing
          artifact-id: ${{ steps.go-action.outputs.cbp_artifact_id }}
▼

After the run completes, the artifact information is displayed in the Run details  Deployments tab in CloudBees Unify.

Related pages

Register GHA build artifacts
Publish GHA test results