-
Notifications
You must be signed in to change notification settings - Fork 84
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
Modernize plugin #64
Modernize plugin #64
Conversation
- Current parent POM - Update dependency to something that doesn't bring a dozen implied dependencies - Corresponding Java level update - Strip redundant parts from plugin name and capitalize it
If you're concerned about the core dependency increase: TBH if it were my plugin, I'd go with a 2.x release, but the main point here is to get rid of the unused implied dependencies to detached plugins. |
Upgrading the core looks reasonable to me. Targetting old cores cause installing unnecessary plugins as you point, and build-timeout is often installed during the setup wizard. I wonder why ci.jenkins.io doesn't test this request even after merging #65 ... |
Test failures caused for
So you can fix the test failures by modifying the log line from And we can replace |
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.
Changes look good to me.
I'd like you to do some additional changes to improve pom.xml and fix tests.
pom.xml
Outdated
<forkCount>1</forkCount> | ||
</configuration> | ||
</plugin> | ||
<plugin> | ||
<artifactId>maven-enforcer-plugin</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.
We can remove also configurations for maven-enforcer-plugin.
- Change fake build step output to prevent false positive build failures - Remove maven enforcer plugin rules from pom
@ikedam I addressed your review comments. |
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.
Looks good to me.
Released build-timeout-1.19. |
@ikedam Thanks! |
@@ -16,7 +16,7 @@ | |||
|
|||
<artifactId>build-timeout</artifactId> | |||
<packaging>hpi</packaging> | |||
<name>Jenkins build timeout plugin</name> | |||
<name>Build Timeout</name> |
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.
This change of name broke JJB as it queries the jenkins master to get the plugin version, and tries to find it by name. I know its a different project, but wanted to post this here in order to note that this change had more impact than expected in a minor version bump.
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.
Relying on the display name that only exists for human use is a terrible idea. Scripts should rely on the immutable artifactId instead.
Tests still pass, otherwise I'm not confident I didn't mess up some of the internals. Review is needed.