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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,991
Community Members
 
Community Events
176
Community Groups

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
TAGS

Atlassian Community Events