Hi Eduard,
There seems to be a bug regarding running jobs on master [1]. Try running it on
a slave instead.
Ramy
[1]
https://github.com/rasselin/os-ext-testing/blob/master/README.md#running-jobs-on-jenkins-master
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, August 05, 2015 5:03 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party-ci]Issue with running
noop-check-communication
Hi,
We're in the process of rebuilding the Jenkins CI for Cinder and i'm stuck at
testing the noop job.
I've setup using the latest changes from os-ext-testing and os-ext-testing-data
using project-config, jjb and dib and i have a jenkins running which has the 2
jobs defined and i have 3 slaves attached (from a devstack - cloud provider).
Now when i make changes to sandbox (to test it) i see jobs being triggered but
they hang in Jenkins:
pending—There are no nodes with the label ‘’http://10.100.128.3:8080/label/
I checked the job config and it shows Restrict where this project can be
run/Label expression master / Slaves in label: 1 and i can trigger it
manually and it shows Waiting for next available executor on master -
although there are 4 executors in Idle.
Any ideas?
Thanks,
--
Eduard Biceri Matei, Senior Software Developer
www.cloudfounders.comhttp://www.cloudfounders.com/
| eduard.ma...@cloudfounders.commailto:eduard.ma...@cloudfounders.com
CloudFounders, The Private Cloud Software Company
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
