Hi. One option to help with this is Dependabot or similar. It can also work
with internal Maven repositories and create PRs automatically when
dependencies have updates available.
to 21. lokak. 2021 klo 17.42 David Hoffer (dhoff...@gmail.com) kirjoitti:
> We have about a dozen applications that
On 17. 10. 21 11:56, Michael Osipov wrote:
> Hi Users,
>
> are there any Maven users who use Maven SCM Hg provider directly or
> indirectly through Maven Release Plugin?
> We are currently reviewing the vast amount of code in Maven SCM and
> try to reduce what cannot reasonable maintain.
We use
trunk based vs gitflow is a well covered subject on the internet, both have
tradeoffs that you need to think about and choose what's best for you.
For us, it was the ability to quickly make a hotfix on the master branch
for production in case a big refactor/change was merged in the develop
branch
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
We have about a dozen applications that use various in-house developed
components which are in a separate component repo. The component repo has
all of the components (currently about a dozen) and is configured so we can
release each one independently from the others. (Some components change
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
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
10 matches
Mail list logo
