When starting new release "Release branch already exists. Cannot start release."

See original GitHub issue

When starting new release with mvn gitflow:release-start I receive an exception because of old-release branch… “Release branch already exists. Cannot start release.” In fact, plugin refuses to create branch “release/1.0.1” because there is branch “release/1.0.0” already existing. What is the correct workflow in case there are many installations of the product with different release versions so all release branches should be maintained? I use <keepBranch>true</keepBranch> because of that. However it causes this exception… Btw. how is it possible to set <keepBranch>true</keepBranch> only for release, release-start and release-finish goals and keep it false for other goals in parent pom? It seems like goal release doesn’t create release branch. It would be nice if it did in case keepBranch=true.

Issue Analytics

State:
Created 7 years ago
Comments:15 (7 by maintainers)

Top GitHub Comments

7reactions

kuhajeyancommented, Oct 9, 2020

we are maintaining multiple release branches, and we dont necessarily delete them once we merge to master. In this case, when we are trying to release-start, we get this “release xxxx already exists. Finish that first!”.

is there any parameter to suppress this existing version check?

0reactions

kngmat004commented, May 13, 2022

I really hope we could work on a separate config item to allow multiple release branches would be another plus for an already great plugin

Top Results From Across the Web

a release branch.. already exists | error while starting the release

So to release the projects from GIT repo, I am trying to use jgitflow-maven-plugin version 1.0-m1 to release the projects off of GIT...

jgitflow:release-finish is not deleting the release branch

But now I am trying to create a new branch using jgitflow:releast-start . But it is giving the below error. [ERROR] Failed to...

Gitflow release branch process from start to finish example

After the “git flow release finish” command runs, the release branch should be deleted and a new Git tag exists in the repository....

gitflow-maven-plugin - Bountysource

When using this, the release-finish is merging release-branch onto master and tagging correctly. Then it merges release-branch onto develop. This doesn't allow ...

Releasing - Argo CD - Declarative GitOps CD for Kubernetes

The target release branch must already exist in the GitHub repository. If you for example want to create a release v1.7.0 , the...