We have several (100s, set to grow as more are migrated from SVN) developers constantly pushing/pulling to/from Stash. On top of this, we have more than 500 plans that have various triggers, most of them poll the repository for changes every minute. This occassionally causes resource issues on the Stash server until the queue of scm tasks is flushed out.
I worked in other orgs in the past that had a Perforce setup with two servers : one main server where devs pushed their changes, and a read-only mirror server that the build servers pointed to, to prevent any resource issues on the main server. Is this scenario possible with Stash?
You have two options:
In both cases, you can use a simple network share or a bare-bones Git server (e.g. GitStack) for hosting the mirrors.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot