Introduced AbstractProject.supportsMakeDisabled rather than using trick of checking for parent instanceof Jenkins.
Extracted common GUI into makeDisabled.jelly, with accompanying I18N refactoring.
Also moved all this into AbstractProject, where the relevant methods are defined, rather than Job where they are not.

- doc improvement
- report the result and the problem to the listener

One of the problems with the current way Jenkins puts JavaScripts is that most everything is in a single file. It doesn't highlight the relationship between those fragments and their corresponding tag files.

So I'm experimenting with moving out these fragments into individual JavaScript files co-located with the tag file. They then get loaded into the page via <st:adjunct>. Each script is served with unique URL such that the browser will not even have to try conditional GET when loading different pages, so this should prevent the performance problem caused by the fact that there are now lots of <script> tags in the page.

 If for some reason even this turns out to be a problem, we can always add additional build steps to concatenate them all.

reapplied the correct fix.

This reverts commit ee645202.
It appears that the author edited this file with UTF-8 encoding when
this file is actually iso-8859-1 encoded

This makes it consistent with other buttons like repeatable-add-button, and use of '-' prevents name collisions with form names, and make all of those UI controls addressible in the same namespace

[FIXED JENKINS-13695]

This reverts commit e2303ef4.

[FIXED JENKINS-13695]

(cloudbees folder plugin as a sample impl)

This code was originally developed for analysis-core plugin, but I think it's useful outside it.
I'm promoting this up to core

Preserve in-progress builds when reloading a job.
Because in-flight builds tend to update the state a lot, with this
change we refrain from reloading those builds from the disk.

This should be acceptable since we are primarily reloading a job, and
reloading of builds are secondary.

All top-level jobs show up in search, as opposed to just jobs in the
current view or in the primary view.