[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39240#comment-39240 ] Eyal Edri commented on OVIRT-2714: ---------------------------------- We have 5 servers, which are shared between CQ, OST check-patch and nightly OST Jobs. so not so much. Is running OST Manually is an option? you can run the same way it run on the manual job. If we see it's not enough, maybe we consider paying for renting external bare metals, or we can also look into moving another server to run inside OpenShift to run more load as I've asked [~gbenhaim@redhat.com] and [~dbelenky@redhat.com], same as KubeVirt runs. Why do you think it's not available? as I said, its probably being taken by CQ or OST check-patch... eventually we have a limited amount of hosts, so i'm not sure there are ideal hosts

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)