This reverts commit 3c471f1f.

This reverts commit 3c471f1f.

Changes "Slaves in label: N" to "Label is services by N slave(s) and M cloud(s)".
Portugese translation reset.

Squashed commits:
[73308b5] [FIXED JENKINS-27549] job loading can be broken by a NPE in a build trigger

(cherry picked from commit 4c0d3ac6)

Squashed commits:
[73308b5] [FIXED JENKINS-27549] job loading can be broken by a NPE in a build trigger

(cherry picked from commit da1c74f6)

[JENKINS-22811] If a project action fails to load we should log the project action and continue to load the project.

(cherry picked from commit c3eb1cac)

(cherry picked from commit 47fa17ba)

Conflicts:
	changelog.html

If a project action fails to load we should log the project action and continue to load the project.

Allow Projects to take the Queue.Item's actions into consideration when determining their default authentication

This changes prevents the improper usage of method without the preliminary supportsMakeDisabled() check.
As an example, Subversion plugin behaves in such way (JENKINS-24341)
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>
(cherry picked from commit a78f1d32)

Adjust my prior change to better utilize structured form submission to accomodate a plugins that are not using p:config-assignedLabel

Adjust my prior change to better utilize structured form submission to accomodate a few plugins that are improperly submitting data through this processing logic

Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>

This changes prevents the improper usage of method without the preliminary supportsMakeDisabled() check.
As an example, Subversion plugin behaves in such way (JENKINS-24341)
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>

By converting several optionalBlock entries to use inline="true", we convert the submitted JSON from:
   "hasPropertyFoo": {
     "propertyFoo": "value"
   },

which is a somewhat unnatural naming scheme, to:
   "hasPropertyFoo": true,
   "propertyFoo": "value",

This enables us to use the pattern:
   if(json.optBoolean("hasPropertyFoo", json.has("propertyFoo"))) {
     ...
   }

To permit either of the following as JSON blobs, for specifying a value for "propertyFoo":
1) "hasPropertyFoo": true,            # What comes through from jelly
   "propertyFoo": "value",

2) "propertyFoo": "value",

It also allows any of the following as JSON blobs, for NOT specifying a value for "propertyFoo":
3) "hasPropertyFoo": false,           # What comes through from jelly
   "propertyFoo": "value",

4) "hasPropertyFoo": false,

5) (nothing specified)

NOTE: The main interest in flexibility in what JSON comes through is in support of: https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin, this is also the purpose of the couple renames that are mixed in with this.

Switch to using inline optionalBlock for several AbstractProject checkboxes so that we are passed a boolean, instead of either null or {}.

NOTE: The discrepancy between inline-optionalBlock and f:entry/f:checkbox is the text alignment, which optionalBlock keeps consistent with other elements (and what is done for these today).

This change shifts the way a number of form elements are accessed when handling AbstractProject's doConfigSubmit from using "req.getParameter(...)" style access to using JSON-style (structured form submission) access through "reg.getSubmittedForm()".

https://bugs.openjdk.java.net/browse/JDK-6933067 claims to be fixed as of Java 6, our baseline.

java.lang.NullPointerException: null
	at hudson.model.AbstractBuild.setWorkspace(AbstractBuild.java:296)
	at hudson.model.ProjectTest.testCheckout(ProjectTest.java:423)

This change improves the handling of errors in hudson.model.Executor, which cause issues like JENKINS-18164.
The change also introduces several annotations in order to prevent further issues.
Signed-off-by: NOleg Nenashev <o.v.nenashev@gmail.com>

Pulling doChildrenContextMenu up from AbstractProject into Job, since the latter already defines permalinks.

Deprecating AbstractProject.ABORT, since it is simply Item.CANCEL anyway, and better documenting this permission and its usage.