The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
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
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Atlassian Community Events
Copyright © 2026 Atlassian