I wonder what is the best approach in the current situation;
In our project we have a set of build, deploy and test jobs. In the nightly build, which takes the full test set (which takes a couple of hours), can eventually can lead to a releasable build
The on-commit build though, uses the same build, deploy and smaller set of test jobs, and is mainly used to provide CI feedback to the developers.
Would there be a way to set this up in 1 flow where only the nightly triggered build takes up all the test jobs, and the on-commit builds to only uses the smaller test set?
This will definitely impact the maintainability of the pipelines, where on changes we don't want to do things twice.
Thanks for providing feedback for us,
In my opinion, I guess it would be better if you have two different plan in one project. As for trigger, it will run the build for the whole plan and can't be specified by only stages. Therefore if you have sets of jobs that specific to specifc trigger, I would suggest you to have two different plans.
Hope it helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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