You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?