* Load i18n resource bundles from plugins if not found in jenkins core
Signed-off-by: Thorsten Scherler <scherler@gmail.com>
* Issue 404 response for missing i18n resource bundles
Currently issues a 200 with an "error" response payload. This change still issues the error response payload, but also sets the HTTP response.
Signed-off-by: Thorsten Scherler <scherler@gmail.com>
* [JENKINS-35845] Fix test since we return now a 404
* [JENKINS-35845] add test for getting locale from plugin. fix comments from oleg.
* [JENKINS-35845] Fix description
* [JENKINS-35845] Update PR with comments from Oleg
* [JENKINS-35845] Add feedback from tom
* eslint - formating changes and fix offences
* eslint - formating changes and fix offences
* [JENKINS-35845] remove code concerning 404 response. Fix resourceBundle test by prevent NPE to happen
* [JENKINS-35845] Link to issue on which we introduced the test
* [FIXED JENKINS-38650] - Cleanup spelling in CLi commands.
Also adds some javadoc and since definitions.
* [JENKINS-38650] - Move common warning message to the constant
* [JENKINS-38650] - DeleteViewCommand should also use the constant string
* [JENKINS-38650] - Rename the constant in order to make the name more explicit
Currently a shell job has to make a HTTP call back to Jenkins to set
its build result as unstable. This is slow, requires the slave to
have access to the master's HTTP interface, and is fiddly. The
alternative, the TextFinder plugin, is no better.
Instead, allow a job to set the build result to unstable with a
return value.
Adds the Advanced parameter "unstableReturn" which, if non-zero,
is the code the script must return to set the build as unstable.
* [JENKINS-36748] Add a test case and not process null specs
* [JENKINS-36748] Correct license and add a minor comment
* [JENKINS-36748] Add a Waning logger when spec is null
* Check that dependencies are enabled. A disabled optional dependency
will not prevent a plugin from loading.
* Check versions of dependencies declared by a plugin before loading it.
If any dependency (even optional) is older than what is required,
then the plugin isn't loaded.
This should prevent use cases where a plugin is loaded but one of its
dependencies is too old so that :
* its @Extension annotated classes cannot be loaded, causing the full
Jenkins to blow up with crapload of exceptions which are tedious to
investigate to understand the root cause.
* NoSuchMethodError and the likes at runtime even though boot has
completed.
Version check (for setups where version list is manually crafted but yet
works) can be disabled by starting Jenkins with
-Dhudson.PluginWrapper.dependenciesVersionCheck.enabled=true
Minor fixes done while implementing this change :
* Fix version parsing in PluginWrapper.Dependency
* Dynamic plugin load didn't check for disabled flag