[Gluster-infra] [Bug 1362471] New: Jenkins should only assign one concurrent job per node

bugzilla at redhat.com bugzilla at redhat.com
Tue Aug 2 09:54:35 UTC 2016


            Bug ID: 1362471
           Summary: Jenkins should only assign one concurrent job per node
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Assignee: bugs at gluster.org
          Reporter: nigelb at redhat.com
                CC: bugs at gluster.org, gluster-infra at 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:

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

More information about the Gluster-infra mailing list