There is advanced option "Enable Repository Caching on Remote Agents" on repository configuration.
But what you may try instead is setting origin in additional task after checkout and before push to your git server.
git remote set-url origin <url>
Until next change detection fires cache will be invalid though.
I already disabled it on remote agents but that wont solve the problem when the plan is run on the main-server. Also setting the remote for git is not possible for me, because I can't (wont) hardcode the URL and using the environment-variable bamboo provides is not working because I have no easy way of adding username:password@ to it. If it was possible to disable repository caching altogether it would be so much easier for me ...
This is also discussed in the Bamboo KB. https://confluence.atlassian.com/display/BAMKB/Merging+and+pushing+to+remote+repository+failsand the issue tracker https://jira.atlassian.com/browse/BAM-11930I have the same problem.
Voting for this issue. I've made a couple of scripts to do fetch/push for me and I just pass them the repository url and the branch(es) to fetch/push. The url is not hardcoded as I use the bamboo variables to give me that. (eg, bamboo.planRepository.repositoryUrl - see https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables) The plan branch name is also passed via bamboo variable, but other branch names do need to be hardcoded. (Luckily it's just develop + master) HOWEVER - The repository cache keeps old branches around which is screwing with jgitflow which now only lets you have one release branch at a time, which means I have to delete the repository cache EVERY time I run the release plan. Seriously screwed up.
The repository cache is a horrible feature. It causes so many problems. Not only do your tags not make it to the remote agents unless you check the remote caching option, but you have to come up with crazy workarounds to the fact that you can't simply release using Bamboo. At this time, I suggest that people do NOT buy Bamboo because of the repository caching. None of these things should be an issue in the first place. The repository caching is horrible and there is no way to disable it.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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