-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3.0.0: requireBranch
property is final and cannot be overridden
#357
Comments
HI, I'm having the same problem. Using
Doesn't work either. The error is:
|
I faced that too, and agree that it's not normal, but the following workaround works:
|
Thank you very much. This worked for me. |
I have the same problem, but with litte different error. release {
// ...
git {
requireBranch = 'master'
}
} Results in the following error: I think that the error from @arjanvlek is related to mine, because the Configuring the following beforementioned workaround in release {
// ...
git {
requireBranch.set('master')
}
} However, this workaround is not intentional. The Gradle Documentation for Lazy Evaluation states: Please provide a fix for the root problem, as this plugin is not conform to Gradle documentation anymore. BTW: The documentation of this plugin in README.md is not correct anymore, as |
FYI, the problem was introduced here in this commit: a4a29c1#diff-e153b6a5c5ad5979271a2f7e4b409cd2357bb11a25d1498d1e374d3cb1eabe77R39-R40 Ping @Hillkorn |
It seems the following also does not work anymore
My release just failed saying I was not on the Strangely enough all commits and the actual release of the artifact went correctly? |
I guess it's because of the final 🤔 @Shuyinsama Your code says "release/.*" is required and not main. |
We're releasing from the
development
branch to themaster
branch.The following configuration works fine in version 2.8.1 of the plugin, but breaks in 3.0.0:
With version 3.0.0, we're getting the following error message:
We need to override the
requireBranch
property, because we are not releasing frommain
(or previouslymaster
) branch but fromdevelopment
. The readme indicates this is still a valid configuration setting, so I wouldn't have expected this to break.Versions I'm using:
OS version is not right, my Intel Mac is running macOS 12.4 so i don't know why it says 11.4.
The text was updated successfully, but these errors were encountered: