Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When will there be an option to disable repository caching?

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.


1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 18, 2019

Bamboo version 6.7 onwards have task to perform Git push.

Bamboo 6.7 release notes

Do you mean that it is not working?

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.

I have seen many discussions online from many people expressions their frustration with the repository caching. So, I would like to know when there will be an option to disable it.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 19, 2019

Feature request to disable repository cache in local agent

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events