Not quite sure how to debug this, or if anyone has seen this as well, but
I've found that using Jenkins versions 1.596.1 and 1.596.2 my Jenkins jobs
would stay in the build queue and were never run. My first thought was the
node/labels were incorrect, but once verified the job still sat in the
build queue. Looking at the information in the hover help for the queued
job gave no insight. I reboot/restarted things many times without any
luck.
I rolled back my jenkins.war version to 1.565.3, recycled everything, then
deleted the queued jobs and everything started flowing as expected. I
picked 1.565.3 as another team is using this w/o issue.
If it matters, I'm just doing my initial testing and I'm running everything
on the Jenkins master, with 4 executors.
I didn't notice anything of the ordinary in the Jenkins logs, but there may
be some additional logging that may be required. Nor did I see anything of
interest in the zuul/zuul-merger/gearman logs.
Any ideas?
Bob Hansen
_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
