On 2016-06-30 12:13:01 +0800 (+0800), 王华 wrote:
> There is a period between a job is done in Jenkins and the node is
> deleted by nodepool. Before the node is deleted, the node can be
> seen on Jenkins.How can Jenkins know not to use the node which has
> already run a job? Is there a mechanism to ensure this case?
The aforementioned OFFLINE_NODE_WHEN_COMPLETE parameter is
interpreted by the jenkins-gearman plug-in and offlines the
corresponding Jenkins slave atomically with job completion so that
there should be no race where it's possible for the master to assign
it another job. That said, if you're running a particularly recent
Jenkins release (1.651.2 or later), there is a new security feature
which prevents parameters from being passed outside of the job
configuration and you'll need to solve that issue in one of several
ways:
http://lists.openstack.org/pipermail/openstack-infra/2016-May/004284.html
--
Jeremy Stanley
__________________________________________________________________________
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
