Details
-
Bug
-
Resolution: Unresolved
-
Major
-
build-flow plugin: 0.9
jenkins: 1.513
other plugins:
ant 1.2 true true
build-name-setter 1.3 true false
build-timeout 1.11 true false
copyartifact 1.26 true false
credentials 1.4 true true
cvs 2.8 false true
email-ext 2.28 true false
external-monitor-job 1.1 false true
git 1.3.0 true false
git-client 1.0.5 true false
github 1.5 true false
github-api 1.40 true false
javadoc 1.1 false true
jobConfigHistory 2.4 true false
join 1.15 true false
jquery 1.7.2-1 true false
ldap 1.4 true true
mailer 1.4 true false
maven-plugin 1.513 false false
nodelabelparameter 1.4 true false
pam-auth 1.0 true false
parameterized-trigger 2.17 true false
s3 0.3.2 true false
sbt 1.4 true false
ssh-credentials 0.3 true true
ssh-slaves 0.25 true true
subversion 1.45 true true
text-finder 1.9 false false
throttle-concurrents 1.7.2 true false
token-macro 1.7 true false
translation 1.10 false true
xpath-config-viewer 1.1.1 true false
build-flow plugin: 0.9 jenkins: 1.513 other plugins: ant 1.2 true true build-name-setter 1.3 true false build-timeout 1.11 true false copyartifact 1.26 true false credentials 1.4 true true cvs 2.8 false true email-ext 2.28 true false external-monitor-job 1.1 false true git 1.3.0 true false git-client 1.0.5 true false github 1.5 true false github-api 1.40 true false javadoc 1.1 false true jobConfigHistory 2.4 true false join 1.15 true false jquery 1.7.2-1 true false ldap 1.4 true true mailer 1.4 true false maven-plugin 1.513 false false nodelabelparameter 1.4 true false pam-auth 1.0 true false parameterized-trigger 2.17 true false s3 0.3.2 true false sbt 1.4 true false ssh-credentials 0.3 true true ssh-slaves 0.25 true true subversion 1.45 true true text-finder 1.9 false false throttle-concurrents 1.7.2 true false token-macro 1.7 true false translation 1.10 false true xpath-config-viewer 1.1.1 true false
Description
The following flow frequently takes a long time before detecting all spawned builds have completed.
build.setDisplayName("#${params['pullrequest']}@${params['sha'].substring(0,6)}>${params['mergebranch']} [${build.number}]") // full, parallelized, Scala PR validation // scala-distpack should run fastdistpack-maven-opt, a new task that skips generating docs parallel ( { retry (2, { build(params, "pr-scala-rangepos") }) }, { distpack = build(params, "pr-scala-distpack") downParams = params + [ 'distpack_build' : "<SpecificBuildSelector><buildNumber>${distpack.build.number}</buildNumber></SpecificBuildSelector>" ] // has to run on same node as distpack for stability test // TODO: have separate job for stability (skip locker in distpack) testParams = downParams + [ 'node' : distpack.build.builtOnStr ] parallel ( { retry(2, { build(testParams, "pr-scala-test") }) }, { retry(2, { build(downParams, "pr-scala-integrate-ide") }) }, // cannot figure out how to add an ignore wrapper here.. { retry(2, { build(downParams, "pr-scala-integrate-partest") }) } ) } )
Here's close to 30 examples:
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1113/
...
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1135/
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1145/
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1146/
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1147/
https://scala-webapps.epfl.ch/jenkins/view/pr-validators/job/pr-scala/1150/
ps: the ignore combinator causes even worse breakage (I wanted to ignore a build in a parallel block, but had to abandon because it caused what looks like races)
