Lazy-loading utility test class designed for fix of JENKINS-15858.
(cherry picked from commit 03ca63c62c1f3e20f405b655bbc610ed21931a86)
[FIXED JENKINS-16023] Use permalinks for as many Job.getLast*Build methods as possible.
(cherry picked from commit be5cd4fd169005f50eea8ccefac4b91a9b4c503c)

Conflicts:
	changelog.html
[JENKINS-18236] Computer.getUrl was incorrect when the slave had a space in its name.
This broke the context menu for actions contributed via TransientComputerActionFactory (at least).
(cherry picked from commit 92d96525240ddc0fdf30a839ada0dd642b34c4ef)
[JENKINS-18352] need to prefer linked files over archives.

This regression appeared to be introduced in 32d5c23.

(cherry picked from commit 7547681a24fadab2a909729413b9f16da90b2d16)
[JENKINS-18352] we want to prefer *.jpi over *.hpi, but the code was other way around

(cherry picked from commit 5aa4af75c2c4c66541f1fd24ef82c5d46a79940d)
[FIXED JENKINS-18356] Restored deprecated AbstractProject.doBuild{,WithParameters} overloads.
(cherry picked from commit fa47981c071bf8c11041d4f11b2be0c73ab0b270)

Conflicts:
	changelog.html
JUnit 4.
(cherry picked from commit 291c39ad42dbd5e2676bc8229051f68f7b33ced5)
[JENKINS-17125] Establishing baseline FingerprintAction behavior that should not be regressed.
(cherry picked from commit bd709b0631329f1abaf05de4a3499562a1606691)
[FIXED JENKINS-17125] FingerprintAction no longer need persist the build field thanks to new RunAction2.
(cherry picked from commit a614cd5b05b3c8cbcb8970ea439b2a1315252f58)

Conflicts:
	changelog.html
Using l:confirmationLink instead of AbstractItem/delete.jelly and AbstractProject/wipeOutWorkspace.jelly.
(cherry picked from commit 7d31e7c5d66b37bf9905cfcec2f13862faaf74b9)
[FIXED JENKINS-17977] [FIXED JENKINS-18032] Fixed confirmPOST JS utility not working with CSRF protection enabled.
(cherry picked from commit 4ec2e08f8ccb2d1e40da45bde9df7f3721ff85c1)
[FIXED JENKINS-17977] [FIXED JENKINS-18032] Added CSRF crumb to actions requiring confirmation only when POST method is used.
(cherry picked from commit b0f867fc9390563df99dbb166f1ebe731fe2b873)
testWipeWorkspace was failing after changes to link confirmation.
Tricky to emulate the actual web interaction including JavaScript window.confirm;
suffices to just call the web method directly.
(cherry picked from commit 2d3fa398c352ddd44a43980766e14e5f8352e0d1)
As this is my first look inside Jenkins codebase I not sure it's correct
but perhaps artifacts for modulebuilds should be deleted just as logs
are deleted. see https://issues.jenkins-ci.org/browse/JENKINS-17508
I did not fully test it yet, all unit tests ran fine, but didn't succeed
to run jobs inside Jenkins, due to classloader issues while running
Jenkins in Jetty, to verify deletion

(cherry picked from commit d4459d9d0f99b951974f6ab1bedf6a580aad9248)
adds test that looks in jobs archive with 2 builds when LogRotator set as build discarder with settings to keep only 1 build with artifacts, test searches for jars in archive for build one and build two expecting no jars in build 1 and expecting jars in build 2

(cherry picked from commit c8f73d0015365ab13a17c18ef8cd750cdcda2506)
add documentation to testcase.
(cherry picked from commit 2a0bd7eebd1ee70aa6099197f48810235ddc9ab0)
also testing the removal of build if LogRotator is configured to discard
old builds and not only artifacts (Not needed for the issue, but an
extra test is not a luxury )
(cherry picked from commit ca7f4e682c8faa024053130d672d28684c010067)
[JENKINS-17508] updated the test to use @Rule and no longer extend from the old HudsonTestCase (shouldn't that one be marked deprecated?), add @ Bug and @ For as jesse suggested

(cherry picked from commit aa1d28b04014c18838e87b3a8b1707cc5eb28b14)
[JENKINS-17508] removed usage of deprecated elements in test
(cherry picked from commit f9ce6558c93d7f7ff0f8df12fb80f9ecc868ff99)
changed the filepath#toUri call to #getRemote as per comment of @jglick

(cherry picked from commit 5661af73698a9ec03b256e1d960ae2ede8bad6d0)