The repository caching of Bamboo is a painful feature. We have had to do so many workarounds because of it. You cannot simply run a release job that pushes changes back to the repository. Instead you have to come up with all kinds of "tricks" to get it to work. This is annoying at best. You should not have to do tricks and workarounds to push changes made by the release plan back to the repository. Yes, I know you can add another remote with scripting, but again this is a trick or workaround and should not be required in the first place.
Then, if you don't check the right boxes, Git tags don't make it to remote agents and the wrong version gets build into the software, when your release process depends on tags.
Thanks for the reply. Unfortunately, the Git push is just a workaround. It is just reifying the other commonly done workarounds for getting around the fact that the repository caches are an obstacle. In our case, as with many people, the project is released by Gradle itself. There is no need for tools external to Gradle for "finishing" the release. The repository cache is preventing a normal Gradle release process from working. If the repository caching can be disabled, then everything will work as it should and there will be no need for all these workarounds.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
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