Setting Artifactory Properties in BuildAndPushDockerRegistry Step
pending feedback
C
Coral Pinniped
We request native support in Harness CI to apply JFrog Artifactory properties (key/value metadata) directly during the BuildAndPushDockerRegistry step.
This would allow setting attributes like environment, application, or release version on artifacts without additional pipeline steps, streamlining workflows and improving artifact traceability.
Log In
ompragash
updated the status to
pending feedback
ompragash
Thanks for raising this. The Build and Push step is backed by the Docker/buildx plugin flow, so the supported configuration surface is Docker-native.
For Docker image metadata, the OOTB Build and Push step already supports labels directly through the Labels field.
For JFrog/Artifactory build information specifically, use the Artifactory Docker Build Info plugin after the image is published. That plugin publishes Docker image build information to JFrog Artifactory, including build details, VCS information, SHA256 verification, build URL, and principal information from the build trigger.
Example:
```yaml
- step:
type: Plugin
name: Publish Build Info
identifier: publish_build_info
spec:
connectorRef: account.ArtifactoryDocker
image: plugins/artifactory-publish-docker-buildinfo
settings:
access_token: <+secrets.getValue("artifactory_token")>
build_name: <+pipeline.name>
build_number: <+pipeline.executionId>
build_url: <+pipeline.executionUrl>
docker_image: artifactory.example.com/DOCKER_REPO/IMAGE_NAME:TAG_NAME
```
Docs: