You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the plugin to create an automated delivery pipeline with Jenkins. I have configured a input in my job to create a release direct from pipeline after performing automated integration tests. I'd like to start a release branch from this, already tested, point (identified by the commit SHA1) and not from the top of develop.
Currently, is possible to achieve this by disabling fetchRemote and creating a local develop branch at the desired location, but it requires extra work. It would be nice if the plugin supported this through a release-start property. Something like the following:
I don't think that the release-finish goal needs to be changed, because the release-start doesn't touch the develop branch. It's exactly the same as adding commits to the develop branch before the release is finished.
Hello @aleksandr-m. Thanks for the plugin!
I'm using the plugin to create an automated delivery pipeline with Jenkins. I have configured a input in my job to create a release direct from pipeline after performing automated integration tests. I'd like to start a release branch from this, already tested, point (identified by the commit SHA1) and not from the top of develop.
Currently, is possible to achieve this by disabling fetchRemote and creating a local develop branch at the desired location, but it requires extra work. It would be nice if the plugin supported this through a release-start property. Something like the following:
mvn -B gitflow:release-start -DInitialCommit=<SHA1>
Would you consider including this feature?
The text was updated successfully, but these errors were encountered: