Prevent PluginServletFilter warnings when running JFR as a standalone JAR #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some Jenkins core and plugin servlet filter initialization routines assume that
PluginServletFilter
is always present within the system. And this is definitely correct for classic Jenkins, but for JFR it was leading to startup warnings and stacktraces.This patch merely adds PluginServletFilter to the virtual Jetty engine. It has almost no overhead, and such trick is easier than changing behavior of the Jenkins core
Fixes #193