Bug 1362471

Summary: Jenkins should only assign one concurrent job per node
Product: [Community] GlusterFS Reporter: Nigel Babu <nigelb>
Component: project-infrastructureAssignee: Nigel Babu <nigelb>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: bugs, gluster-infra, mvignesh
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-17 09:57:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nigel Babu 2016-08-02 09:54:35 UTC 
We currently have concurrent: yes for most jobs, because if we didn't it wouldn't run two jobs simultaneously on multiple machines. While we want concurrency, we also do not want two jobs on the same machine.

The key is to use this: http://docs.openstack.org/infra/jenkins-job-builder/properties.html#properties.slave-utilization
Comment 1 Nigel Babu 2016-08-17 09:57:35 UTC 
Done!