[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39238#comment-39238 ] Eyal Edri commented on OVIRT-2714: ---------------------------------- The manual job has already 10 available executors: job-template: name: '{project}_manual' project: '{project}' concurrent: true properties: - build-discarder: days-to-keep: 14 - throttle: enabled: true option: project max-total: 10 The fact that jobs are waiting in queue means there aren't enough hosts to run the tests, something that isn't easily solvable without buying new hardware or perhaps moving the manual job to run on containers instead of single bare metals servers. [~gbenhaim@redhat.com][~dbelenky@redhat.com] how much time will it take to move the manual OST Job to run on containers, something that might help here?

Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs -------------------------------------------------------------------------------------------

Key: OVIRT-2714 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra

This one is about manual OST runs cloned from OVIRT-2704 --- 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)