Please disregard, this appears to be an issue with Brakeman output step
which was included via template. It seems to have triggered the following
bug. https://issues.jenkins-ci.org/browse/JENKINS-22779
Thanks!
On Sunday, August 17, 2014 11:40:26 PM UTC-5, Chris Meisinger wrote:
>
> Hi!
>
> I'm trying to do a proof of concept parallel build and running into an odd
> issue. Am I missing something here?
>
> The following DSL is what I'm using...
>
> ----
> parallel (
> { build("test1") },
> { build("test2") }
> )
> ----
>
> I have two jobs, test1/test2. They are basic git clones and then a build
> step that runs an 'exit 0' in the shell. When run individually, they pass
> as expected. When the buildflow job is run, I see the following console
> output, and the job never finishes, however both test1/test2 jobs complete
> successfully. It looks like it's waiting for 'test2' to finish, which it
> does, but the signal gets lost somewhere.
>
> ----
>
> Started by user Me
> parallel {
> Schedule job test1
> Schedule job test2
> Build test1 #7 started
> Build test2 #10 started
> test1 #7 completed
> -----
>
>
> Cloudbees buildflow plugin ver: 0.12
> Jenkins version: 1.575
>
>
> Thanks!
> Chris
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
