-
Notifications
You must be signed in to change notification settings - Fork 52
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
Introduce EdDSA-api plugin #3230
Conversation
as mentioned in the upstream PR that attempted to do this unconditionally this is broken by design. the JTH and tests assume that the classpath is correctly setup however it is not, as demonstrated in the prior commit. According to Jenkins there is a plugin installed (trilead-api) because it is in the megawar, however its classess are not in the flat classpath used by JenkinsRule and thus breakage ensues. ref: jenkinsci/plugin-compat-tester#470 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the weekly-test is not reporting issues, this looks good.
I expect issues similar to this (for which an issue will be filed along with a fix) |
Just as you said, it fails exactly where you said it would. |
Head branch was pushed to by a user without write access
The particular error mentioned in #3231 could be solved in |
@@ -33,6 +33,10 @@ | |||
<groupId>io.jenkins.plugins</groupId> | |||
<artifactId>byte-buddy-api</artifactId> | |||
</dependency> | |||
<dependency> | |||
<groupId>io.jenkins.plugins</groupId> | |||
<artifactId>eddsa-api</artifactId> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: the original intent of this file was to include only dependencies that were actually used “naturally”, not transitive deps. This was never mechanically enforced, though, and has proven difficult to manage: #683
Do not pass the Fat War to the JTH to avoid random issues with plugins being present (yet missing classes) that should not be present, or present and unexpected (ie failing when a given system property is set by JTH)Testing done
None, to be tested in CI
Submitter checklist