Docker Pipeline (JFrog)

Build and tag Docker images using JFrog Artifactory Docker with dynamic naming, output parameter reuse across steps, and optional linking to an upstream build step's resources.

Register the JFrog Artifactory Docker tool in Opsera's Tool Registry before configuring this step.

Prerequisites

• JFrog Artifactory Docker tool registered in Opsera Tool Registry

• Jenkins tool registered and a job created for Docker builds

• SCM account with repository access configured

Pipeline Setup

1

Create a Docker Step

Click +. Step Setup: Tool = JFrog Artifactory Docker. Save. Open Step Settings and select the Jenkins Tool, Job Type, and Tool Job.

2

Link to a build step (optional)

Toggle Use Build Step Resource on to inherit the SCM account and repository from an existing pipeline build step. Choose the step name from Build Step Info. If disabled, select Account and Repository manually.

3

Configure dynamic naming

Toggle Use Dynamic Docker Name on. Choose a source (e.g. Branch Name) — the selected value is automatically used as the Docker image name.

4

Configure tagging

Toggle Dynamic Tag on. Options: Commit SHA, Branch Name, or Build Number. For SHA: enable Specify Limit on Commit SHA Characters, set Trim Direction and Character Limit (e.g. 8). Use Add Multiple Docker Tags for static alias tags.

5

Map output parameters Add Output Parameter mappings to pass Docker image name/tag details into downstream pipeline steps. Values update on every run automatically

Configuration reference

Field	Description
Use Build Step Resource	Inherit SCM account and repo from an existing build step
Dynamic Docker Name	Auto-populate image name from Branch Name or pipeline values
Dynamic Tag Type	Commit SHA, Branch Name, or Build Number
Commit SHA Trim Direction	First N or Last N characters of the SHA
Output Parameter Mapping	Expose Docker image details to downstream steps

Points to remember

• Use Build Step Resource is the recommended approach when a Maven or Gradle build step already exists in the pipeline — it avoids duplicate SCM configuration.

• Output Parameter Mapping values are updated on every pipeline run — downstream steps always receive the most current image tag without manual updates.

• Commit SHA trimming to 8 characters is the Git standard for short references and is sufficient for Docker tag uniqueness in most CI environments

FAQs

What is the difference between Docker CLI and Docker Pipeline Steps?

Docker CLI is a standalone step that handles build and push independently. Docker Pipeline (JFrog) is specifically designed to integrate with JFrog Artifactory and supports richer parameter reuse with upstream build steps.

Can I use both Static and Dynamic Tags together?

Yes. Enable Dynamic Tag for the version-specific tag (e.g. commit SHA), then use Add Multiple Docker Tags to add a static tag like latest simultaneously.