I'm seeing something a little weird in one of my workflow jobs, and I'm not
sure if I'm doing something wrong or if it's a bug. Basically I have a top
level job that's coordinating several component jobs. The top level job
monitors several repos (right now it's just polling every 5 minutes) for
changes, and when it sees changes, it kicks off the component jobs.
However, what I'm seeing is the top-level job is running multiple times for
a single change. The only thing I can think of for what's happening is that
the change isn't getting recorded as having been built before the next
polling cycle runs, because the top-level build hasn't finished. Is that a
reasonable assumption, or should I Iook somewhere else for the problem? An
outline of the top level build is below, if that helps.
checkout([/* details for repo1 */, subdir: 'repo1'])
checkout([/* details for repo2 */, subdir: 'repo2'])
checkout([/* details for repo3 */, subdir: 'repo2'])
archive 'repo1/'
archive 'repo2/'
archive 'repo3/'
c1 = build([job: 'component-1'])
c2 = build([job: 'component-2'], params: [[$class: 'RunParameterValue',
name: C1_ARTIFACTS, runId: c1.id]])
c3 = build([job: 'component-3], params: [[$class: 'RunParameterValue',
name: C1_ARTIFACTS, runId: c1.id],
[$class:
'RunParameterValue', name: C2_ARTIFACTS, runId: c2.id]])
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/3667cfee-0598-47f6-8f00-b09405193904%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
