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?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.