These issues are fixed with pull request #166 that we just merged.

Added a new WipeOut permission (enabled through the hudson.security.WipeOutPermission system property) to control the "Wipe Out Workspace" action

HTTPS

[FIXED JENKINS-9203] in light of 9c965617, I think the proper fix is to define a mechanism to abort with status.

backporting this from the trunk.

We weren't actually enforcing the initialization order at all, as
sorting was based on the plugin name.

$JENKINS_HOME if it exists.

See
http://jenkins.361315.n4.nabble.com/LDAPBindSecurityRealm-groovy-td3584243.html

This change is largely based on changes made by Winston Prakash for Hudson.
The main details about his changes can be found here:

http://issues.hudson-ci.org/browse/HUDSON-8844

I deviated a bit from his changes where it was appropriate (e.g. the
description for allow-signup.html was just plain wrong). Also, there
was a lot of collateral damage from formatting in his changeset, which
I have factored out.

I tested the basic functionality of this change and it seems to be OK.

more gracefully.

[FIXED JENKINS-9807] : [Maven Jobs] Post build deploy task : Deploy with unique versions (timestamp) should be configured by default

ViewGroups like NestedView to override)