We need to 'lock' our branch_dev during the nightly build process. This is to prevent any merges during build time because if build is successful, that code line is then merged into a branch_int, at which point the branch_dev can then be 'unlocked'.
I thought I'd use the stash cli and test doing this with the updateBranchPermissions, but I get a java lang exception:
I put the wrong output, below is the correct stash cli I passed and it's output:
stash --action updateBranchPermissions --project "SCOT" --repository "ScottTestRep" --id "5" --branch "branch_dev" --userId "33"
Picked up _JAVA_OPTIONS: -Xmx512M
I can't find any error being reported in the stash logs. Am I doing something incorrect?
In short, build starts, have our jenkins builder account have branch permissions. Build is over, update branch permissions to the original branch users.
If there is a better way to about this, please let me know.
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