We have multiple developers working concurrently and make use of a development server to review the state of our application.
We push to the "dev" branch to trigger a pipeline to deploy all approved changes to this server. This deploy triggers a new build of the current state of the app.
When we are developing rapidly there may be several deploys triggered concurrently which bogs down the deployments with redundant building.
How can we have the latest/most recent deploy automatically cancel previous deployments in progress?
We'll be looking into ways to solve this problem natively in Pipelines later this year.
I suggest you following this ticket for updates: https://bitbucket.org/site/master/issues/12821/limit-concurrent-pipelines-so-deployment
In the meantime, if you need this functionality now, you can use the Bitbucket Pipelines REST API to construct a script that checks for other, more recent, running pipelines before deploying.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot