Onboard
Introduction
Users
Teams
Introduction
IntroductionPromote an image in Amazon ECRRetrieve an object from Amazon S3Store an object on Amazon S3Copy Docker images with CraneDownload a file from JFrog ArtifactoryMove or copy an image from JFrog ArtifactoryUpload a file to JFrog ArtifactoryGet artifact detailsManage artifact labelsRegister a build artifactRegister a deployed environment artifact
IntroductionCreate or update a functionInvoke a function
IntroductionRun an AWS CodePipelineRun a Bamboo projectRun a Bitbucket pipelineRun a CloudBees CI jobRun a CircleCI workflowRun a GitHub Actions workflowRun a GitLab pipelineRun a Harness pipelineRun a Jenkins® jobRun a JFrog pipelineBuild and publish Docker images with KanikoRun a TeamCity project
IntroductionMigrate from v1 to v2
IntroductionAWS credentialsECR credentialsEKS credentialsGit global credentialsOCI credentials
IntroductionRun Ansible PlaybookDeploy with Argo WorkflowsDeploy with AWS CodeDeployDeploy a binary with Amazon EC2Deploy to ECSRender an Amazon ECS task definitionDeploy with AWS Elastic BeanstalkDeploy with HerokuDeploy with OctopusDeploy with OpenShiftDeploy with SpinnakerDeploy with Tosca
Publish evidence items
Fetch secrets from CyberArk Conjur
IntroductionHelm chart installHelm chart packageHelm chart publishHelm chart uninstall
IntroductionCreate a Kubernetes namespaceCreate/update a Kubernetes resourceDeploy to a Kubernetes cluster
IntroductionVerify with NewRelic
Execute remote commands via SSH
IntroductionAnchoreAquasecJFrog XraySnyk ContainerSonatype (Nexus) ContainerTrivy
IntroductionStackhawkZAP
IntroductionCheckmarxCheckovCoverity on PolarisFind Security BugsGitHub Security ScannerGosecGrypeMendNexus IQnjsscanSnykSonarQube bundledSonarQube
IntroductionBlack DuckMendSnyk
IntroductionGitleaksTruffleHog ContainerTruffleHog CodeTruffleHog S3
IntroductionCreate a change requestUpdate or close a change requestGet a change request current stateQuery a change request approval
Publish test results
Multi-workflows dispatch
Introduction
Get started with feature flags
Create flags in code
Manage multiple SDK keys in your application
Create and manage flags in the UI
Namespaces and labels
Configure feature flags
Feature management custom roles
Flag approval requests and reviews
Audit history
Get started with configuration as code
Set up configuration as code
Configuration as code reference
Configuration-as-Code examples
Flag impressions and activity status
Flag health
Code references
Properties and custom properties
Target groups
Enabling secret mode
IntroductionAndroid / Android TV / Fire TVC/C++ (client-side)C/C++ (server-side)GoJavaJavaScript (browser) / Chromecast / TizenJavaScript SSR.NET/C#Node.jsiOS / tvOSPHPPythonReact NativeRuby
IntroductionClient-side AndroidClient-side C ClientClient-side C++ ClientClient-side JavaClient-side JavaScript (browser)Client-side .NET/C# clientClient-side Objective-CClient-side React NativeClient-side SwiftServer-side CServer-side C++Server-side GoServer-side JavaServer-side .NET/C#Server-side NodeJSServer-side PythonServer-side PHPServer-side RubyBoth client-side and server-side JavaScript SSR
IntroductionAndroid appAngular appDjango appGin appJava Spring Boot app.NET Core appReact appSwift iOS app

Integrations

2 minute read

CloudBees Unify supports Jira integrations for feature traceability, which link associated work items (such as tickets and user stories) to component build artifacts. For more information about Jira integrations for feature traceability, refer to Feature traceability.

Create a Jira integration

Use the following steps to create an integration:

  1. Navigate to Components  Integrations.

  2. Select Create integration. The create integration screen displays.

  3. Select the integration type from the dropdown list provided. The fields required to create the integration display.

  4. Enter the required information for the integration type:

    1. Select the appropriate Jira instance from the dropdown list provided. The dropdown displays the list of Jira integrations from the parent organizations.

    2. The domain field is autopopulated based on the Jira integration selected.

    3. Select the purpose of the integration from the dropdown list provided.

    4. Select the appropriate Jira project to associate with this component.

    5. Select pattern to identify Jira ticket reference in commit message. This pattern will be used to associate the Jira tickets to build artifacts through the commit associated with the build artifact.

    6. Enter the SCM repository branches as a comma-separated list to be considered when associating Jira tickets to build artifacts.

      • If left empty, only commits on the default branch are considered.

      • Branch names can include * as a wildcard. For example, main,release_v considers the main branch and all branches starting with release_v.

  5. Select Save configuration.

Edit an integration

Use the following steps to edit an integration:

  1. Navigate to Components  Integrations.

  2. Select the Vertical ellipsis next to the integration to edit.

  3. Select Edit. The edit integration screen displays.

  4. Edit the required information for the integration type:

    1. Verify or select the appropriate Jira instance from the dropdown list provided. The dropdown displays the list of Jira integrations from the parent organizations.

    2. Verify the domain is correct for the Jira instance selected.

      1. Select Manage to manage Jira instances.

    3. Verify or select the purpose of the integration from the dropdown list provided.

    4. Verify or select the appropriate Jira project associated with this component is listed.

      1. Select Change project to select a different Jira project.

    5. Verify or select the pattern to identify Jira ticket reference in commit message. This pattern will be used to associate the Jira tickets to build artifacts through the commit associated with the build artifact.

    6. Verify or select the SCM repository branches as a comma-separated list to be considered when associating Jira tickets to build artifacts.

      • If left empty, only commits on the default branch are considered.

      • Branch names can include * as a wildcard. For example, main,release_v considers the main branch and all branches starting with release_v.

  5. Select Save configuration.

Delete an integration

Use the following steps to delete an integration:

  1. Navigate to Components  Integrations.

  2. Select the Vertical ellipsis next to the integration to delete.

  3. Select Delete.

  4. In the confirmation dialog, select Delete to confirm deletion of the integration.