Bug 1362471 - Jenkins should only assign one concurrent job per node
Summary: Jenkins should only assign one concurrent job per node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 09:54 UTC by Nigel Babu
Modified: 2016-08-17 09:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-17 09:57:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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!
Note You need to log in before you can comment on or make changes to this bug.