https://bugzilla.redhat.com/show_bug.cgi?id=1362471
Bug ID: 1362471 Summary: Jenkins should only assign one concurrent job per node Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: nig...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org 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 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fLNF541Xfo&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra