We have code deployed to our staging servers upon every commit to develop branch.
In situation when two commits are put into develop quickly one after another, two deployment processed are started almost simulateously and interfere with each other.
I have overcome this problem by setting up a lock mechanism in our deployment script using flock command.
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