Turns out in the new executor on-demand code, queue maintenance happens so quickly that even when a job is submitted with delay 0,
it can still fail the test if the check happens when "new GregorianCalendar()" returns the same value as "top.timestamp".

I'm relaxing that check

Integrating the stapler fix.

Consult Descriptor.newInstance() even when proccessing is in the middle
of JSON tree.
(cherry picked from commit d15c1550)

Noting that various DirScanner implementations handle this inconsistently.

[FIXED JENKINS-18836][FIXED JENKINS-18879][FIXED JENKINS-19619] Upgrade trilead-ssh to version with the fix

the page used FilePath.getLocal(), which was removed in
19860fa0 (12/2006)

Both are shown if defined. The edit description link only applies to View.description.
Properly handle a ViewGroup other than Jenkins itself, such as a folder.

[FIXED JENKINS-19920] Using selfReference to mean “none” from nextBuild/previousBuild was just asking for trouble.
JENKINS-16194 and an analogous but opposite bug fixed more simply by introducing a separate NONE constant.
Also numberOnDisk did not get updated properly after a build was deleted, causing double loading of build records in some cases.

Conflicts:
	maven-plugin/pom.xml
	plugins/pom.xml
	ui-samples-plugin/pom.xml

This reverts commit d15c1550.

Consult Descriptor.newInstance() even when proccessing is in the middle
of JSON tree.