The article on scaling stash mentions that ref advertisements may be cached, but it warns that plugins which update the repository automatically might cause a stale refs cache and fetch operations to fail.
(Looking at your website, googling, and looking at other questions here, I couldn't find an answer to this question)
From Atlassian's article on Scaling Stash for continuous Integration performance ( https://confluence.atlassian.com/stash/scaling-stash-for-continuous-integration-performance-329352840.html ) :
As a precaution, ref advertisement caching is disabled by default. The openness of the plugin system means that plugins (or manually installed git hooks) could be updating refs in repository without the caching plugin detecting these changes. The result would be a stale refs cache and failing clone/fetch operations. However, if you know that there are no plugins or git hooks installed that make changes to the repository directly, you can enable the ref advertisement caching using the system properties listed in the Configuration section below. Note that as an additional precaution, the ref advertisement caches are configured to automatically expire after a minute.
Probably Related: https://answers.atlassian.com/questions/16392783
Workzone uses the public Bitbucket API when auto-merging Pull Requests. This is technically the same as if you click the merge button in the UI. Changes will be propagated by BB server internally.
Workzone does NOT perform SCM level write operations directly to repositories at any time. That's all done by the code underneath BB's public PullRequestService API.
Hope that clears things up.
It looks like you're new here. Sign in or register to get started.
![Photo of Ulrich Kuhnhardt [IzymesDev]](https://us.v-cdn.net/6038660/uploads/avatars/6d/13/n6d1300a6a94689c3eca00678a7bbb49f.png)