I have the following scenario:
Here's the issue:
(P2) stage#2, download specific artifact, even though I've picked the specific named artifact from the list of shared artifacts on the parent plan, seems to be re-assessing the copy pattern at the time it attempts to download. As the copy pattern has a bamboo.buildNumber variable in it, the download is using the buildNumber from (P2), not the buildNumber of (P1) that was used in the naming of the original artifact's nuget package.
so the artifact in (P1) has a filename: "projectName.0.1.3.83.nupkg", but the stage#2 download seems to be looking for "projectName.0.1.3.94.nupkg".
Doesn't Bamboo keep a reference to the actual file that the specific artifact on the parent plan relates to? Or does it use the original plan's pattern match and substitute in its own values?
Is there a better way to achieve what I'm trying to do?
I might add, that plan (P1) also has plan (feature) branches, which need to be built in order to update feature stories on Jira with their build status, but only the primary branch needs to have the UI tests run against it, hence the child plan, linked only to the primary branch.
Do you need the variable-filled copy pattern in P2S2? Shouldn't you already only have the package you want in the directory you are dealing with? Could you use a simpler copy pattern of * projectName.*.nupkg or something there instead? (I assume you have dumped the available bamboo environment variables in P2S2 and didn't see anything for the parent's buildNumber?)
Hi there! Shannon from Statuspage here. 👋 With Cyber Monday quickly approaching, we're looking to hear from Atlassian customers – specifically from teams who touch incident response li...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs