Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Pipelines with multiple maven-release-plugin

I have a monorepo which has multiple projects and each project has it's own POM. Each project uses the maven-release-plugin to generate a snapshot/release version.

I have a single bitbucket-pipeline.yml to configure the steps - but I am hitting a problem when releasing multiple projects from the same pipeline execution.

As you can imagine, if I release project A, a git commit is created with the new POM versions. When I then try and release project B, the git clone command always resets to the hash which triggered the pipeline.

This means the git commit on the POMs for Project B fails as the git repo is now behind.

Has anyone solved this?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events