You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Consider the following use case where we are running a multi-branch pipeline that is having 3 new branches within it(i.e branch1, branch2, and master maintaining the same build name & number) and maintain a single buildinfo object in Artifactory by publishing it from each branch.
Publish buildinfo of the first pipeline branch to Artifactory
Then, download the existing buildinfo of the above build from Artifactory and append it to the current buildinfo of the next branch, and publish it again to Artifactory.
Similarly, download the latest buildinfo (for the above build number) from Artifactory and append it to the current buildinfo, and publish it to Artifactory.
Describe the solution you'd like to see
Currently, appending a published build-info into an unpublished build-info is not supported. Hence, Looking for an option to download buildinfo object which was published as part of the previous build stage, and append it to the current stage build object so that we can maintain an aggregated buildinfo of the multi-branch pipeline.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
tataraov
changed the title
Add support for appending a published build-info into an unpublished build-info using the jenkins-jfrog-plugin
Add support for downloading published Artifactory build-info object from Artifactory and append using the Jenkins-jfrog-plugin
Feb 28, 2023
@tataraov,
The build-info is immutable by design. However, you can logically add a published build as a module to the current build. This feature is named build-append.
For more information see Aggregating Published Builds.
Is your feature request related to a problem? Please describe.
Consider the following use case where we are running a multi-branch pipeline that is having 3 new branches within it(i.e branch1, branch2, and master maintaining the same build name & number) and maintain a single buildinfo object in Artifactory by publishing it from each branch.
Describe the solution you'd like to see
Currently, appending a published build-info into an unpublished build-info is not supported. Hence, Looking for an option to download buildinfo object which was published as part of the previous build stage, and append it to the current stage build object so that we can maintain an aggregated buildinfo of the multi-branch pipeline.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: