-
Notifications
You must be signed in to change notification settings - Fork 111
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
Reduce applicability requirements #32
Conversation
// Moving category to categories, to support, well, multiple categories per job. | ||
@Deprecated transient String category; | ||
|
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.
Please avoid such formatting changes to simplify merges
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.
Sure, I will get rid of them. Actually, I removed them manually before commit, but IDE put them again :)
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
You probably want to implement |
Good point, I haven't thought about it. Will provide the update soon. |
@jglick, hmm... On second thought, ParameterizedJobMixIn is there since 1.556, while TCB is built against 1.424. Also, JobProperty's generic parameter must extend Job, so I'm bound to extend the ThrottleJobProperty class from JobProperty < Job > (can't use ParameterizedJobMixIn.ParameterizedJob, as it doesn't extend Job). |
Personally I don't like the
In any case, the core dependency update may be reasonable. Versions 1.535...1.609.2 do not behave reliably, so probably bumping to 1.609.2 is the best option. The plugin needs some redesign, so please do not consider the version dependency as a blocker. |
So, what should I do next? |
Dependency update is perfectly fine, yeah. |
fwiw, tested this and it works fine throttling groups of Workflow jobs - not being used within the Workflow script, though. That's more work, which I'll get diving into once this is in. |
👍 for the current implementation |
Rightie-o, then I'll merge it. |
Reduce applicability requirements
Thanks for merging! |
Hi,
We have a project type, which does not extend AbstractProject, but directly extends Job and implements Queue.Task (we have certain reasons to not extend AbstractProject). We would like to have the Throttle plugin working with it, but it's tied to AbstractProject.
This pull request unties it from AbstractProject class and makes so, that the Throttle plugin works with any class which extends Job and implements Queue.Task.
This is just a technical patch, no new features added.