Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Problem Definition
When queueing a build that contains an Artifact Download task, Bamboo will check the currently available artifacts and add them to the build metadata. Though this works on most of the build scenarios, in case a build is queued/triggered outside of a Build Dependency chain – such as queueing sequential build plans manually and expecting that the generated artifact from the first build will be consumed by the second one, and so on – the consuming builds will refer to the artifacts that were available before the queueing time, and not the latest, generated by the producer build that had just finished.
Suggested Solution
Add an option to the Artifact Download task that will allow the user to choose if Bamboo should try to use any newly available artifacts that may have been produced after the Build's queueing time.
Workaround
- Configure an Artifact dependency relation between Jobs of the same Plan. An artifact dependency is not an "Artifact task"; it is a Job's Artifact configuration step that happens before any tasks are executed; that way, when consumer Jobs are started, all the selected artifacts from the creator Jobs are automatically copied to the current work directory of the consumer Jobs so they have the files to work on.
or - Setup Plan build dependencies to create a build chain sequence. Bamboo will then use the artifact produced by the latest build, which ran immediately before the dependent build was queued.