Fixed check if docker image already exists.
(option -q will only output numeric ids, but we need to check the image tag)
support another version that lets you set the reason.

Also changing the locator to be bit more robust in case more buttons get added here)
Improving the diagnostics
This field name has changed since LDAP plugin 1.9.

See a68bf21b79fc7eaa50a1301817b8c64c063eea0c in ldap-plugin repo
setLabels may be called immediately after SlavesMixIn.create, at which time we are in /createItem, not /computer/*/configure.
Merge branch 'master' of github.com:jenkinsci/acceptance-test-harness
Javadoc.
Comment.
waitUntilStarted (and thus shouldSucceed and other methods) should visit the Jenkins home page while they are waiting, so you can watch the queue and executor widgets etc.
Otherwise you merely get to see a blank page from /job/*/build?delay=0sec, which is not very helpful.
Reducing the number of RUN

... as I appear to be hitting 42 aufs limitations
Can no longer extend from NodeParameter

... as it has acquired more methods that only makes sense for that type
Added Slave.waitUntilOnline as a convenience to tests creating slaves directly.
Merge branch 'master' of github.com:jenkinsci/acceptance-test-harness
Describe the failure.

These matchers look at the console output, so better to just dump them
Fixing an assertion.

On my Ubuntu 12.04, vncserver is tightvnc, so the output looks like the following:

    Terminating xvnc.
    $ vncserver -kill :77
    Killing Xtightvnc process ID 7868
    Finished: SUCCESS

Since vncserver output is fragile, It's better to assert on the output from the plugin.
Mark some tests as smoke tests. Uses JUnit a category to identify a smoke test.

Run theses tests to get a first impression if everything is still working as expected.
This commit marks five tests as smoke test: XML remote API validation, Java Script and table tests, docker fixture, maven project, slave creation.
Merge branch 'docker_build_fix' of https://github.com/eidottermihi/acceptance-test-harness
Tweaking the relative path resolution rules.

Sometimes we come across the path expression that ends with "/" like "/attributes[1]/" --- those are select controls
that produces different config fragments depending on the option selected.

We want to be able to create such references via control("/").
Note that control("") is already used throughout for referring to a path without "/" in the end, so we need to keep that working
added binding for mock security realm
Started adding AuthorizationStrategy for matrix-auth