tree c76ae4c12786b7b4b45067c915737e20bb71f488
parent 940453e873f0e1a070cb9da0743e7f1d642cf44a
author Dennis Dmitriev <ddmitriev@mirantis.com> 1527789439 +0300
committer Dennis Dmitriev <ddmitriev@mirantis.com> 1527791653 +0300

Add waiting for the correct build_id in the JenkinClient:run_build()

If the job is queued while waiting for the free executors, then
the method was getting the wrong build_id belonging to the
previous job, for instance it will return build_id=28 in this example:

  №2​9 (pending—Build #28 is already in progress (ETA:17 min))
  №2​8 [In progress]  May 31, 2018 6:07 PM

* Add 'timeout' parameter (default 600sec) in run_build()
  to wait until the queued build is started
* Add pooling the queue until the build is started, get the
  build number assigned to build in queue object
* Add 'verbose' parameter (default False) to show the reason
  from Jenkins why the build is not started yet, for example:

    pending the job 'deploy_openstack' : Build #22 is already in progress (ETA:1 min 48 sec)
    pending the job 'deploy_openstack' : Build #22 is already in progress (ETA:1 min 18 sec)
    pending the job 'deploy_openstack' : Build #22 is already in progress (ETA:48 sec)

* Rename the parameter 'print_job_output' to 'verbose'
  in the method wait_end_of_build() to have the common parameter
  naming.

Change-Id: Id49b5b45a8127e769b89860b19424081f37f6f38