Unlike [JENKINS-14514] this is a true fix rather than a workaround (now removed), and is more general.
cjo9900 discovered that behaviors were being redundantly registered (as of 1.474 the monolithic JS is broken up);
this caused some behaviors to be run repeatedly on the same elements, breaking reasonable expectations of some behaviors.
The ideal fix would be to change Behavior.register to be idempotent: for example, key it by selector, then maintain a set of distinct behavior functions for each.
Unfortunately some adjuncts directly call Behavior.list.unshift, bypassing register(...), which would be tricky to intercept (would need to make a mock of Array).
The known one cases are in core, but it is possible plugin adjuncts do this too, in which case it would be incompatible to (say) change the Array<Map<String,Behavior>> to a Map<String,Array<Behavior>>.
Instead, permitting redundant registrations as before, and just silently skipping all but the first at runtime when applying behaviors.
Beware that since adjuncts are loaded from multiple places, different JS function objects are registered each time, so a naive set of behavior functions does not work;
have to identify functions by their toString in order to ensure that each is run only once.
(Currently once _per selector_, conceivably >1x per element; could if necessary be refined to make sure a given behavior is only run once on a given element during one call to applySubtree even if the element matches multiple selectors.)

Displays transient user actions in the User sidebar
Displays UserProperties that are also Action in the User sidebar

[FIXED JENKINS-13916] Text parameters are now defined and shown in a textarea instead of a one line textbox.

Add @Exported annotation to the executor of a Run to have more information on a running Job via the remote API

Uninstall.command is dropped to /Library/Application Support/Jenkins

Fixed a problem in actually making concurrent builds work.

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.

[FIXED JENKINS-13695]

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.