The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Enforce merges to master
We use Jira, Jenkins and Bit Bucket to build, deploy and version our code. The problem is using Jenkins pipeline the user build and stages a release for production. We run the Jenkins portion that actually deploys the release. The Jenkins pipeline then waits for users to validate the push to production and if okay they press a button that does a merge-tag-delete of that release to master in Bit Bucket. However sometimes the don't do their part so now master doesn't match production. Is there anyway to setup Bit Bucket that upon requesting a pull or a commit that because they didn't merge the release if will prevent them from making any further changes. Maybe a SQL script that lists all releases that haven't been merged?
Thanks
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.