Bumping up to the latest remoting
[JENKINS-24436]

Fixing a test failure.

https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/361/ reports 8 consective failures on this test case because of the following assertion error:

    Expected: is "job/archaeological_replacement/checkstyle"
         but: was "/view/difficult_style/job/archaeological_replacement/checkstyle"

IIUC, the spirit of the test (and the bug reported in JENKINS-24436) is to make sure that the link correctly takes the user to the report page. I think the test would be more robust and sufficient if we just check that, instead of insisting on a relative url vs path-absolute URL.
Click the link and verify that it takes the user to the report page.
Active Directory test should attempt to use "Test" button

All tests attempt to use the "test" button before setting security.
When test button fails, the test should exit without touching the
security realm.
Update scenarios in tests javadoc.
Added a mechanism to exclude tests by placing a magic file 'excludes.txt'
1.0.3 pom is botched, so upgrading to 1.0.9

1.0.3 POM has a snapshot dependency:

[INFO] +- com.github.jnr:jnr-unixsocket:jar:0.3:compile
[INFO] |  +- com.github.jnr:jnr-ffi:jar:1.0.3:compile
[INFO] |  |  +- com.github.jnr:jffi:jar:1.2.8-SNAPSHOT:compile
[INFO] |  |  +- com.github.jnr:jffi:jar:native:1.2.8-SNAPSHOT:runtime
[INFO] |  |  +- org.ow2.asm:asm:jar:4.0:compile
[INFO] |  |  +- org.ow2.asm:asm-commons:jar:4.0:compile
[INFO] |  |  +- org.ow2.asm:asm-analysis:jar:4.0:compile
[INFO] |  |  +- org.ow2.asm:asm-tree:jar:4.0:compile
[INFO] |  |  +- org.ow2.asm:asm-util:jar:4.0:compile
[INFO] |  |  \- com.github.jnr:jnr-x86asm:jar:1.0.2:compile
[INFO] |  +- com.github.jnr:jnr-constants:jar:0.8.4:compile
[INFO] |  \- com.github.jnr:jnr-enxio:jar:0.4:compile
The path name in this case cannot be hard coded

... as it changes in the presence/absence of other plugins.
Geb PageObjects should be instantiated via Guice

... which lets us bridge Geb page objects into existing Java page objects for logic reuse.
Wrong hard-coding of numbers.

Jenkins with different plugins installed will not have the same list of SecurityRealms and AuthorizationStrategies in this order.
Better to reuse the logic implemented in GlobalSecurityConfig.

In general I don't think it's wise to rebuild parallel page object tree just for Geb. Instead, we should figure out a way
to bridge existing Java Page objects into Geb, for example by having Geb PO delegate to Jenkins PO. They all build on the
same WebDriver, so this should be quite possible.
Active Directory test should attempt to use "Test" button

All tests attempt to use the "test" button before setting security.
When test button fails, the test should exit without touching the
security realm.
Update scenarios in tests javadoc.
Merge pull request #20 from houchker/AD-TestButton

Active Directory test should attempt to use "Test" button
ActiveDirectorySecurityRealm#testButton -> ActiveDirectorySecurityRealm#validateConfig
Missing import.
Newer versions of the compiler plugin do a better job of reporting errors.
7c801e1f7a9c84c28317e04daf902c8483708760 by @kohsuke was incorrect: missing cast.
Switched from Groovy to Java to diagnose and verify fix, but in fact switching back does not work;
there is *another* missing cast in the code generated by the buggy Groovy stub compiler.
Since there seems to be no particular reason for this to be written in Groovy in the first place, leaving as Java.
Capture page text only once in hashContent matcher
Select describable class
Test Docker build step plugin
Update SlaveController doc
Run docker on remote slave