happens sometimes on initial "triggerJob", and most likely on "getExecution" .. simple try/catches around each instance of object use, and force fail after X retries depending on where failure occurred ..
issue only occurs when triggering identical parallel jobs in jenkins ..
i bumped down the wait period from 5secs to 1sec .. but that was more for internal purposes ..
is related to this issue: https://github.com/vbehar/jenkins-rundeck-plugin/issues/4
happens sometimes on initial "triggerJob", and most likely on "getExecution" .. simple try/catches around each instance of object use, and force fail after X retries depending on where failure occurred ..
issue only occurs when triggering identical parallel jobs in jenkins ..
i bumped down the wait period from 5secs to 1sec .. but that was more for internal purposes ..
thanks, greg