[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39193#comment-39193 ] Anton Marchukov commented on OVIRT-2704: ---------------------------------------- [~bkorren@redhat.com] [~dbelenky@redhat.com] [~ederevea] [~gbenhaim@redhat.com] any technical reasons "standard-manual-runner" job was made non-concurrent? Anything we may face besides the hardware resources constraint?

Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs ----------------------------------------------------------------------------------------

Key: OVIRT-2704 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra

We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)