[~it12lsp] thanks for reporting that. Yes, any Jenkins version that is running git plugin 4.0.0-rc and git client plugin 3.0.0-rc will see this problem. A fix is proposed in a [pull request|https://github.com/jenkinsci/git-plugin/pull/689] that adds a test for this specific case and reverts the fix for JENKINS-19022 as the way to fix the failing test. That pull request has not been merged yet because I need to write tests for the other 2 blocking bugs that seem to be related. Those bugs are JENKINS-56176 and JENKINS-55939.
I don't plan to require any change to the git tag message plugin at this time, since the issues from the JENKINS-19022 fix seem more serious than I had initially realized. I did not discover them in my testing, nor did several others that were testing, but the community discovered them when 4.0.0-rc was incorrectly released.
The git plugin 4.0.0-rc release has been blacklisted so that it no longer appears in the update center. It should not be used on production servers.
Christian Häussler thanks for reporting that. Yes, any Jenkins version that is running git plugin 4.0.0-rc and git client plugin 3.0.0-rc will see this problem. A fix is proposed in a pull request that adds a test for this specific case and reverts the fix for JENKINS-19022 as the way to fix the failing test. That pull request has not been merged yet because I need to write tests for the other 2 blocking bugs that seem to be related. Those bugs are JENKINS-56176 and JENKINS-55939.
I don't plan to require any change to the git tag message plugin at this time, since the issues from the JENKINS-19022 fix seem more serious than I had initially realized. I did not discover them in my testing, nor did several others that were testing, but the community discovered them when 4.0.0-rc was incorrectly released. The git plugin 4.0.0-rc release has been blacklisted so that it no longer appears in the update center. It should not be used on production servers.