Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
Description
Issue Summary
Currently inside the Artifact download task we have the option to select the Artifact name either individually or All artifacts.
What happens is that not all artifacts are "Required" in order for the build to pass all the time, but are selected to "Shared" so it is available in other builds and deployments. This means that in a scenario where we have two builds:
Build 1:
- Created two artifacts
- A simple script to write/create a file.
- One artifact has a .txt extension and the other one .jar.
- The .txt is selected as "Shared" and "Required", while the .jar is selected just a "Shared" but not "Required".
Build is successful
Build 2:
- Created an Artifact download task
- Selected to get “All Artifacts”
Once we run the build it fails, since the .jar artifact does not exist and with the "Shared" option checked on the .jar artifact that is not required, this behavior is expected. Because if we "aMake the artifact available to be used in other builds and deployments. If you subscribe to an unavailable shared artifact, the build will fail.
Suggested Solution
If we could add an option to download the "All Available Artifacts" artifacts and not just "All Artifacts" or individually.
Attachments
Issue Links
- mentioned in
-
Page Loading...