Description
Is your feature request related to a problem? Please describe.
It is often incredibly useful and needed to find what artifact is attached to what build and what VCS url, revision, and branch. For Docker pushes, these properties do not get attached when utilizing JF CLI and in turn https://github.com/jfrog/setup-jfrog-cli while when utilizing the Artifactory Jenkins plugin we do see these properties attached.
We see these properties get attached in a generic upload but not a jf docker push.
Describe the solution you'd like to see
When utliizing jf docker commands to push an image in addition to the build name and number that gets attached the VCS properties should be attached as well if they are available.
This should mirror what happens with when you do a generic upload.
- Collect the VCS properties through a bag command.
$ jf rt bag derekp-gen-u-test 1
$ jf rt u test.txt derekp-generic-local/test.txt --build-name=derekp-gen-u-test --build-number=1
- Navigate to where the file was uploaded and observe that it has the build.name, build.number, build.timestamp, vcs.branch, vcs.revision, and vcs.url. This is what is desired for jf docker push commands as well.
