[JIRA] [build-flow] (JENKINS-20741) Build has been executing for null in Build-flow jobs

[roberto.gonza...@blue-tc.com (JIRA)]

Roberto González created JENKINS-20741 Build has been executing for null in Build-flow jobs Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 24/Nov/13 5:19 PM Description: If the user makes a flow that has a N jobs in parallel (N given by another job, or param), the main job cant calculate the time that the actual build has been executing. Example: def jobB= { tests= parallel( (0..lastPos).collect { ctr > return { ignore(UNSTABLE) { ejec= build ( "JOB_TEST", params like array[ctr]...) } } } ) } //we launch the builds def job2= { [ jobA, jobB ].each{it()} } parallel(job1, job2) } this example launchs job1 and job2 in parallel, and job2 triggers jobA, and then N builds of jobB, where N is the size of an array. so we have main job -->-->job1------------------> --jobA->jobB(1)--/ -jobB(2)---/ and N builds of jobB. If we have this example, when the main job is running, we hover the mouse in the loading bar of the job we can see "Build has been executing for null" Project: Jenkins Labels: plugin build-flow Priority: Minor Reporter: Roberto González

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.