Low I have a repository with a post-commit hook to trigger a release build on Bamboo 2.5.1. The release build is set to a Trigger Build Strategy, and uses a Maven2 builder to run the following:
mvn -B release:prepare release:perform
This will cause Bamboo to checkout from the repository, build, tag the release, and then commit the next development snapshot to the repository. Once the build has finished, Bamboo starts in on another build, and will continue in this "build, commit, build, commit" loop until manually canceled.
I thought at first this was the post-commit hook's fault, so I removed it, but left the build strategy as Trigger Build Strategy. I then manually triggered the release build from within Bamboo. Same result... an infinite build loop.
Taking a look at the code, it seems like DetectChangesAfterBuildCompletedListener is the culprit, because it explicitly fires a ChangeDetectionRequiredEvent if the build strategy is TriggeredBuildStrategy. There's probably a good reason for this, but for me, it's a blocker on integrating Bamboo any further into our build process.
I verified this to be the case for both Git and Subversion repositories.
- is related to
-
BAM-10693 Allow Bamboo to ignore commits with certain commit messages
- Closed
