Hi - we are 10-15 developers all working on the same repos with lots of pull requests to master.
Our current setup is Bitbucket with Jenkins to run our pipeline to guarantee that everything builds and unit tests are passing before any pull request to master can be approved. We also only allow fast-forward merges.
So this means that everytime someone merges to the master every other pull request is invalid and have to rebase/merge from master before they can try again.Since the pipeline takes anything from 15 minutes to 35 minutes before a pull request can be approved it means that sometimes the same pull request has to go through a lot of iterations before it can finally be merged. The classic "rush to master" issue...
It would be nice if there was a way to reserve a timeslot where only YOU can merge, so that you can be guaranteed to get your changes in, without going around the office to make sure no one else merges ahead of you.
Or do you have another solution or idea for this problem?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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