-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
None
The artifact download is great and wildly useful. However, one feature that would make it amazing is the option to build the copied artifact first.
OR
Just have an outright task of "Build other Bamboo Plan" and make that block the current plan.
Currently in Bamboo, you can set up parent/child relationships. This is fine if you don't mind triggering the parent each time, which in turn will trigger the child plan. But what if I just want to click a child plan, and because it depends on a parent, not have to worry that parent gets built first. Currently, there is no way to force a parent plan to build no matter what. It would be grand to give the user that option.
[BAM-14817] Artifact Download task should have option to 'Build Artifact' first.
J.R. Hass
added a comment - Krystian – Fair question; sorry, not trying to be difficult.
We have several libraries that have very active development going on with all of them.
So much so, that it does not make sense to do a new build of the libraries for every single push.
We also have some applications with the same sort of development, that depends on different libraries.
The bottom line, to not keep the build machines from constantly building, we'd like to do manual builds of both libraries and applications.
When we do a build of an application, we'd like to force a build of the library(s) that it depends on to guarantee we have the most recent code.
Some libraries support several applications, but when we build a library, we don’t necessarily want to build all of the applications that need it;
we’d really only like a library to be built when an application that needs it is being built.
Krystian — your solution would be perfectly valid if our libraries were more mature, but at the current state, it’d be nice to have the fine tuned control over what builds when.
J.R. Hass
added a comment - Krystian – Fair question; sorry, not trying to be difficult.
We have several libraries that have very active development going on with all of them.
So much so, that it does not make sense to do a new build of the libraries for every single push.
We also have some applications with the same sort of development, that depends on different libraries.
The bottom line, to not keep the build machines from constantly building, we'd like to do manual builds of both libraries and applications.
When we do a build of an application, we'd like to force a build of the library(s) that it depends on to guarantee we have the most recent code.
Some libraries support several applications, but when we build a library, we don’t necessarily want to build all of the applications that need it;
we’d really only like a library to be built when an application that needs it is being built.
Krystian — your solution would be perfectly valid if our libraries were more mature, but at the current state, it’d be nice to have the fine tuned control over what builds when. Can you describe scenario when you'd need such feature and explain why can't you rely on latest build's artifact in the other plan?
Hi,
Thanks for your suggestion. Unfortunately it is unlikely that we implement this feature request in the upcoming releases. We're trying to streamline and simplify the user experience in Bamboo and there is a high risk that this development would go against it.
The current workaround forces more builds to happen in your scenario but on the mid and long term we feel that it will be a better solution for you and your team as it will reduce the number of manual steps and the possible errors resulting from it.
Thanks,
Sten Pittet
Bamboo Product Manager