I have a Maven 2/3 build job that runs a pre-step action. The pre-step action calls a Scriptler plugin script which launches the same job. The job is allowed to have concurrent executions. The reason is that on a git commit I want to run the job twice: once with full unit tests, one without. This all works very well. The no-tests build is obviously a lot faster than the full tests build.

However, with HipChat enabled as a post-build action on this job, the second instance (no tests) that is kicked off by the Pre-Step Scriptler action, hangs at the "channel stopped" message. What I've discovered is that removing the HipChat plugin from post-build stops this behavior, and the no-tests (faster) execution of the build job is then able to complete without waiting for the "parent" (if you will) job to complete.

The two executions of the build job are completely independent and nothing is requesting that one wait for the other. But something in the HipChat plugin is forcing it to wait.

Note this can be reproduced in any fashion where you launch concurrent build jobs and a first executes the second. If the HipChat plugin is enabled in Post Build, then the second (launched by the first), will wait.

Please let me know what further information you might need.