- And thus, adapt the code due to the breaking changes in JTH sub-lib

Avoid archiving any test-related artifacts

grammar: bring

* Centralize Descriptor extension list retrieval in DescriptorExtensionList

* Switch to protected way of retrieving ExtensionList

* [JENKINS-55361] Correct DescriptorExtensionList lock to match Descriptor ExtensionList

* [JENKINS-55361] - Add comment to explain using the custom lock (and to retrigger CI)

https://en.oxforddictionaries.com/usage/bring-or-take

> The essential difference between these two words is that bring implies movement towards someone or something

> Whereas take implies movement away from someone or something

Installation wizard: replaced analysis plugins with Warnings Next Generation Plugin

Improvements for translation-tool.pl

* Default methods for RootAction
- reduce code in tests

* - simplification of some existing tests

* - change from RootAction to Action

* - change from Action to a new DefaultRootAction

* using InvisibleAction with the final removed

* adapting the javadoc of InvisibleAction and so remove the usage for non-test class

* [JENKINS-48220] Avoid recursive search for a given view/folder

* Moved to the JenkinsRule

* Moved commented code as JenkinsFile

Bulk cleanup of code in hudson.cli.

Address quiet period edge case (???)

* Add 'smoke-test' JUnit Category [JENKINS-53925]

* Update test-annotations version to 1.3

* Use org.jvnet.hudson.test.SmokeTest

* Try to clarify the message

Key points:
A. We aren't changing the remote update site
B. It's probably possible for this code to forget an ignore if you follow this process:
 
1. suppress a warning for plugin-x-warning-y
2. disable plugin-x
3. suppress a different warning
4. reenable plugin-x

* Trying to clarify where the warnings appear

* incorporating feedback from daniel

markdown

[FIXED JENKINS-54903] Ensure the authenticator is created on load path also

Optimize FilePath.readToString

Restore mis-remove localization files

English

When a node is back to normal, log as INFO instead of WARN

JENKINS-53284 Fix warning message for changing workspace directories

I think the other way round is acceptable as a WARNING.
I think when a node becomes available again, INFO is enough (even more
given Jenkins has INFO as displayed by default)

creation-date (not legacy tokens) + reset + date (not of tokens)

Also reordering the line and dropping a comma