-
Bug
-
Resolution: Unresolved
-
Minor
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)
}
}
)
}
//we launch the builds
def job2= { [ jobA, jobB ].each
}
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.
the schema of the job is attached as a image
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"
[JENKINS-20741] Build has been executing for null in Build-flow jobs
Roberto González
created issue -
Roberto González
made changes -
| Attachment | New: schema-jenkins.JPG [ 24734 ] | |
| Description |
Original:
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" |
New:
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. the schema of the job is attached as a image 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" |
| Assignee | Original: Nicolas De Loof [ ndeloof ] | New: Damien Nozay [ dnozay ] |
Damien Nozay
made changes -
| Assignee | Original: Damien Nozay [ dnozay ] |
| Workflow | Original: JNJira [ 152550 ] | New: JNJira + In-Review [ 178249 ] |