What is the benefit/reason to do the release on a separate branch? Since I have learned we can bypass the BB PR process for approved users it seems our problems will be solved. We aren't currently using gitflow or any advanced GIT process. We just use branches for PRs (they are removed after the merge) and for bug fix releases off from tags/master.
-Dave On Thu, Oct 21, 2021 at 8:38 AM Jeremy Landis <jeremylan...@hotmail.com> wrote: > Try doing your release on a separate branch instead of using master or if > you have jenkins pipeline or other automated build system, let it do the > release with user account that does not have that requirement. Bitbucket > allows a user whitelist. > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android<https://aka.ms/AAb9ysg> > ________________________________ > From: David Hoffer <dhoff...@gmail.com> > Sent: Thursday, October 21, 2021 9:29:45 AM > To: Maven Users List <users@maven.apache.org> > Subject: Best Maven practices for releasing components/applications when > the SCM requires PRs? > > 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 >
