cloud_stack job config fails to recognize complete child jobs

[John George]

The baseline CI Jenkins has a parent job called cloud_stack. Cloud_stack starts child jobs to perform various steps required to bring up a cloud. There is shell logic in cloud_stack's job config that waits until an expected results file is created, in a common results directory, before moving on to the next phase. For example:

timeout -s INT 30m bash -c -- "until [ -f /var/lib/jenkins/results/.*/COMPLETED ]; do echo -n .; sleep 2; done" || exit -1

Periodically this check fails to recognize the COMPLETED file has been created and falls into the exit -1 case. Upon inspection, it can be seen that the file was actually created, in the expected location and within the timeout period.

[Greg Lutostanski (lutostag)]

Fixed by using trigger-parameterized-build plugin @ https://code.launchpad.net/~lutostag/cdoqa-system-tests/+git/jenkins-jobs/+ref/use_params