The subject is wrong. SCM does not require PRs, your SCM suite does.
This is a difference.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
gt;
> > Sent from my Verizon, Samsung Galaxy smartphone
> > Get Outlook for Android<https://aka.ms/AAb9ysg>
> >
> > From: David Hoffer
> > Sent: Thursday, October 21, 2021 9:29:45 AM
> > To: Maven Users List
> > Sub
21 9:29:45 AM
> To: Maven Users List
> 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 Maste
Get Outlook for Android<https://aka.ms/AAb9ysg>
From: David Hoffer
Sent: Thursday, October 21, 2021 9:29:45 AM
To: Maven Users List
Subject: Best Maven practices for releasing components/applications when the
SCM requires PRs?
Our SCM is BitBuck
We use gitflow so a develop branch with "1-SNAPSHOT" version and a master
branch with a fixed maven version in it. We have a script to handle the
merge from develop->master and bump the appropriate version based on the
previous one. It's all automated in a script that is run on jenkins to be
able
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
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
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
