-
Notifications
You must be signed in to change notification settings - Fork 94
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
Use the standard Timer rather than our own ScheduledExecutorService #84
Conversation
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.
See my comments on #81 for why this is not the best solution and probably should be accomplished via shutdown hook / Terminator.
Again, I'd hesitate to trim back the thread pools that we have created to protect as Bulkheads to protect the (heavily used) Jenkins Timer thread pool from misbehaving Pipeline work -- especially when that work is tied to network operations that carry extra risks.
Now, if we made the Timer pool more robust and able to scale up/down, that might be another story.
I think you misunderstand. This is watch-mode code, running in the agent JVM. (Assuming you are running the |
Removes the code added in jenkinsci#86 which is not needed here.
CI flakiness… |
…ugin into standard-thread-pool
BTW @car-roll this had no label, so appears without category in https://github.com/jenkinsci/durable-task-plugin/releases/tag/493.v195aefbb0ff2. Need to make sure to apply one before merging. There is probably some GH Action out there which enforces this…if you can find one which works reliably, is easy to configure, and works properly with forks (should I guess just add a failing Check if there is no label?), then please suggest an addition to the recommended workflow skeleton for JEP-229 in https://github.com/jenkinsci/.github/tree/master/workflow-templates (CC @timja). |
Analogous to jenkinsci/workflow-durable-task-step-plugin#81 but this time reverting a bit of complexity in #60. Together they seem to solve the
RestartableJenkinsRule
problems in jenkinsci/ant-plugin#32.Timer
should work fine in agent JVMs (it does not reference Jenkins model classes); the difference is for durable tasks (in watch mode) run on the master node:Timer
gets properly shut down when Jenkins exits, and is thus safe for in-process restart tests. Again unlikely to have any meaningful impact in production.