Technically we should doing so only after the server reported success, but unfortunately there's no good hook for that.

Added a test case in an attempt to isolate the root cause of the problem, but this one works as expected. Hmm.

Merge remote-tracking branch 'origin/pr/934'

Jenkins with folders A job A/j
a top-level view to recurse into subfolders and include all available jobs and folders (so A and A/j)
=> builds for A/j are included twice, as view.builds iterate on its items, so get A/j + builds from A.

Simplify assertions since webClient#getPage already throws an exception

Replaced tabs by spaces

Should follow this statement:
"Called after a job has its configuration updated."

Should follow this statement:
"Called after a job has its configuration updated."

JENKINS-17108. This solves the problem with ItemListner.onUpdated not being called if the project was disabled/enabled by pushing the button on the project page. Also solved the problem with ItemListener.onUpdated not getting called if the project description was updated using the edit description on the project page.

in case of erroneous http status code.

Hetero list sample

Bump args4j to 2.0.23 as an alternative to #776

Checking that links generated in ListView are valid

[FIXED JENKINS-9637] Fixed the 404 when clicking the testResult on the Project Page when there is only an aggregated test result.

[JENKINS-18723] Fixed performance bottleneck. Corrected the formation of...

Instead it was being thrown in a Future that the master did not wait for:
the writing side failed with a closed pipe exception, and this meaningless error was thrown up.
Fixing by waiting for the reading side first, so any error there will be thrown up.
(If there was _also_ an error on the writing side, we would miss it, but typically this will just be the closed stream.)

[JENKINS-18723] Fixing performance bottleneck, first step. There were 2 times relative path for the job was asked which was replaced by a single time and saving the result in a var.

[FIXED JENKINS-19332]

[FIXED JENKINS-19391] Trying to show the annotation on an Advanced block in newly inserted dynamic section failed since the span is not yet registered.
More generally, suppressing customizedField detection when attrs.field is null;
this prevents us from giving false positives for complex forms with Java-based defaults like CoberturaPublisher.