This came from Alpha CSP guys during JUC Israel. The remote API needs to expose a better way of tracking a submitted task.

[FIXED JENKINS-17125] FingerprintAction no longer need persist the build field thanks to new RunAction2.

[FIXED JENKINS-15652] “Solving” errors by just return null from ALLRM.search and reducing to one-line warnings.
@kohsuke confirms that the intent of throwing AIOOBE was to track down definite code errors;
but in at least some known occurrences of this bug, the problem is invalid data:
build records on disk with <number>s that are duplicated and/or out of order.
Since that violates the precondition of the class, we do not pretend to successfully search for such records.
At some point it would make sense to have the code detect anomalous conditions and initiate a builds folder cleanup.
Take only the last build of a given number, and discard any earlier with higher number.
I.e. just set <number> to 0 or something and ignore such builds, or rename build.xml to build-broken.xml.

Note that when workaround is active, table will not get sorted properly.
Probably OK since tables with large contents that *need* sorting probably take longer to finish rendering.

[FIXED JENKINS-18118] Introduced UserAvatarResolver.resolveOrNull to properly produce fallback icon URL.

[FIXED JENKINS-18074] Avoid clearing AbstractItem.displayName when the new parent ItemGroup is different.

Amends lvotypko’s 33e0df78 to be as careful as bdff4254 + f65da7f9 + 10e9b002 for persistent actions.

Based on the work of Michael Elkin [1].

[1] https://issues.jenkins-ci.org/secure/attachment/20588/0001-tag-1.414-for-parameters-in-multiconfig-filters.patch

changelog entry for JENKINS-17858

changelog entry for JENKINS-17723

[FIXED JENKINS-17681] Do not try to call resolveSymlink on a nonexistent link as you will just get an IOException, breaking peephole permalinks in some Windows environments.