Jesse Glick

This is now actionable again, back to my to-do list…

To avoid confusion, please rename the Jira issue and this PR to clarify that you are patching the executor widget, not the build queue widget.

What the screenshot in the PR description does not show is all of the other stuff in `/manage/` which does not look like “settings” to me: **System Log**, **Load Statistics**,...

> whether this will actually work on a CI machine It does. But it is not any faster than trunk, because each `kind-*` branch runs in its own VM with...

`KubernetesPipelineTest.dynamicPVCWorkspaceVolume` [failure](https://ci.jenkins.io/job/Plugins/job/kubernetes-plugin/job/PR-1495/4/testReport/org.csanchez.jenkins.plugins.kubernetes.pipeline/KubernetesPipelineTest/Tests___kind_1___dynamicPVCWorkspaceVolume/) :eyes:

Could not reproduce the test failure locally even without using the new M2 mounting stuff (which CI does not now use). Can see if https://github.com/jenkinsci/kubernetes-plugin/pull/1550#discussion_r1599973932 helps…

> we don't know what the replacement Security API is yet JEP 411 does not propose a replacement. The whole point is that the concept is outdated and more trouble...

@pfirmstone this is not the right place to give feedback on JEP 411 itself. The point is that, assuming the proposal is accepted (and it is currently targeted for Java...

If a handful of applications continue to use `SecurityManager`-related APIs, despite being `@Deprecated`, with a Java 17+ target, their maintainers already have a straightforward workaround: use an older version of...

> you're not one of the developers and must be a user like me Correct, and I apologize if my wording implied otherwise. I am just offering an opinion as...