-
Notifications
You must be signed in to change notification settings - Fork 200
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
Gradle version check broken #299
Comments
Hi @GFriedrich Is the check printing the wrong result or is this just a code observation? Below is the constructor of The complete class for Hope this helps. Thanks.
|
Hi @dje1990, this was just by reading the code, but nevertheless the checks are not correct in DependencyUpdatesReporter. Lines 176 to 177 in 323dd95
You've said:
But if you check the lines, this is not what the code is doing: The Hope this makes it more clear. |
Hi @GFriedrich I agree I think that the code is incorrect, I have created a fix in #302 |
Thanks! |
@dje1990 can you please look into this test failure? I tried to release for Gradle 6, but unfortunately the CI failed (which also pushed the release to jcenter).
|
This might be a different failure.. need to investigate... |
Hi @ben-manes |
sorry, it's all perfect. thank you. It does seem that the tests got flaky somehow, maybe due to TravisCI changing Linux versions. I had to re-run the CI build twice before it released, with different errors each time. So that is concerning, but each looked like they were flaky due to making external calls. Not worth worrying about for now. |
To me the following two lines look weird:
gradle-versions-plugin/src/main/groovy/com/github/benmanes/gradle/versions/updates/DependencyUpdatesReporter.groovy
Lines 176 to 177 in 323dd95
It seems that the releaseCandidate check is being executed when the release channel is set to "RELEASE_CANDIDATE" and the nightly check is executed for "RELEASE_CANDIDATE" OR "NIGHTLY".
I would have expected the check the other way around (or at least no nightly check for "RELEASE_CANDIDATE").
Funny thing is: The nightly result is never printed for "RELEASE_CANDIDATE", as the checks are done correctly within the PlainTextReporter class.
The text was updated successfully, but these errors were encountered: