That is great news. We don't have a specific CI user yet but your approach sounds great and we will investigate this, it seems the best and simplest solution.
Just curious do you do releases manually via command prompt or do you automate the process with your CI tool? We use Jenkins but releases are manual so far for us. -Dave On Thu, Oct 21, 2021 at 7:44 AM <[email protected]> wrote: > Hi Dave, > > Does this maven-release part of your workflow runs on CI? If yes, you can > manually allow specific users to push directly to master, that's what we do > on our end. We have a specific restricted CI user that we manually allow on > the branch permissions in bitbucket with write access and keep the PR > restriction for the rest of the users. > > On Thu, Oct 21, 2021 at 9:30 AM David Hoffer <[email protected]> wrote: > > > Our SCM is BitBucket/GIT and normally it does not allow Pushes to Master, > > have to Push to a branch and then do a PR to merge to Master. However > this > > doesn't work with the maven release plugin so we have to turn off the PR > > requirement when performing releases. > > > > What are the best practices for managing this? We would like to avoid > > having to manually turn something off and then back on again. > > > > Is there a way the plugin can manage this? Is there a different release > > plugin that can handle the PR process? > > > > Does anyone know if the BitBucket PR process can be bypassed for certain > > users using the maven release plugin? That might be the simplest > solution > > if that is possible. > > > > -Dave > > >
