We're using Bamboo Specs to maintain the definitions of 30+deployment plans.
All those plans are stored in single Bitbucket repo. And this repo is a base for a Bamboo build plan.
Every time we run the build plan, the code is checked out from the repository and "mvn -Ppublish" is executed.
The issue is that with every build all deployment plans are published (=changed) (and audit logs are generated), even though in most cases only one or two deployment plans were actually modified.
Is it possible to publish the changes only for plans which were actually modified?
Which version of Bamboo do you use? We've addressed this problem in version 6.6, if you are on an older version please consider upgrading.
If you happen to use v6.6 or later please let us know which version it is, so that we can investigate possible buggy behavior.
We have the same issue. We are just starting to use Java Specs and have only 4 plans stored in a single repository.
Each time I change a spec for a plan bamboo updates all of them. I see that from the notification sent by bamboo, and from build results of all spec plans - the square icon instead of the round one that says the specs have been updated.
Is that behavior OK, and can I do anything to publish only changed plans and not to see the "Specs configuration updated" on all spec plans?
G’day Bamboo customers, The wait is over! Bamboo Data Center edition you have been asking for is finally here! This self-managed enterprise offering of Bamboo has the resilience, reliability, and s...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events