JFrog integrations

Create a JFrog Artifactory integration to connect CloudBees Unify to your JFrog container registries. This integration enables implicit scanning of artifacts published to your JFrog package management system, helping you identify security vulnerabilities and maintain artifact integrity. Once you connect your JFrog Artifactory to CloudBees Unify, you can trigger automated scans of container images through your CI/CD workflows.

Create an integration

Create an integration between CloudBees Unify and JFrog Artifactory to enable binary scanning capabilities. To integrate with JFrog Artifactory:

Select an organization, and then select menu:Configurations.
Select Create integration.
Select Container registries.
Select JFrog Artifactory.
Enter the following information:
- An integration Name (no spaces are allowed).
- (Optional) A Description.
- The Hostname/IP of your JFrog Artifactory instance.
- Enter the Port number for your JFrog Artifactory instance.
Select an Authentication type:
- Username/Password: Enter your JFrog username and password.
- Personal access token: Enter your JFrog personal access token.
Select Submit.

Your JFrog Artifactory instance is now connected to CloudBees Unify, and the integration is listed under Integrations.

Trigger binary scans

Once the integration is created, you can start scanning artifacts published to your JFrog package management system.

Binary scanning for JFrog Artifactory currently supports container registry artifacts only. The Kaniko build step does not automatically report artifact data to CloudBees Unify.

Binary scans triggered through JFrog Artifactory integration are currently supported for:

CloudBees CI
Jenkins
CloudBees Unify workflows

Configure scan triggers

To trigger a binary scan of artifacts in JFrog Artifactory, configure artifact registration in your CI pipeline or workflow.

Using Jenkins

Use the registerBuildArtifactMetadata step in your Jenkinsfile. This step creates a build artifact record and triggers an automated binary scan.

For detailed information on configuring the registerBuildArtifactMetadata step, refer to Register and view build artifacts.

Using CloudBees Unify workflows

Use the cloudbees-io/register-build-artifact action in your workflow, pointing the artifact URL to your JFrog Artifactory location. This action registers the artifact metadata and triggers an automated binary scan. For detailed information on configuring the register-build-artifact action, refer to Register a build artifact. The following example workflow demonstrates registering an artifact from JFrog Artifactory:

apiVersion: automation.cloudbees.io/v1alpha1
kind: workflow
name: My workflow

on:
workflow_dispatch:

jobs:
build:
steps:
- name: Checkout
uses: cloudbees-io/checkout@v1
id: checkout
- name: Register an artifact with {PRODUCT}
uses: cloudbees-io/register-build-artifact@v2
id: register
with:
name: myApp
url: cb.jfrog.io/myrepo/myimg:1.0.0
version: 1.0.0
- name: Print output parameter artifact ID
uses: docker://alpine:latest
shell: sh
run: |
echo "artifact ID for myApp:${{ cloudbees.version }} is: ${{ steps.register.outputs.artifact-id }}"▼

When artifact registration executes successfully, CloudBees Unify:

Registers the build artifact metadata.
Initiates a binary scan of the artifact in JFrog Artifactory.
Reports scan results in CloudBees Unify analytics.