[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39195#comment-39195 ] Daniel Belenky commented on OVIRT-2704: --------------------------------------- AFAIK, this job is limited because it never meant to be used as a production job, but as a way to debug things or specifically run some scenario. Nir, can't your tool work directly with the OST manual job? it already allows some concurrency and I guess we could increase it. Otherwise, I don't have any strict objection on increasing the # of concurrent jobs in the manual runner other than that IMO, it wasn't meant to be used in this scenario and it will be hard to find jobs there.
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)
On Thu, Mar 21, 2019 at 3:59 PM Daniel Belenky (oVirt JIRA) < jira@ovirt-jira.atlassian.net> wrote:
Daniel Belenky commented on OVIRT-2704: ---------------------------------------
AFAIK, this job is limited because it never meant to be used as a production job, but as a way to debug things or specifically run some scenario. Nir, can't your tool work directly with the OST manual job?
We use OST manual job to run OST. But we need to build the artifacts for OST, and the only way this can be done now via the API is using the manual runner. Please see the entire flow here: https://github.com/nirs/oci/blob/master/system-tests.py
it already allows some concurrency and I guess we could increase it.
Otherwise, I don't have any strict objection on increasing the # of concurrent jobs in the manual runner other than that IMO, it wasn't meant to be used in this scenario and it will be hard to find jobs there.
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) _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W7Z7ANY3PUTUYV...
I have no objections to increase it. I've updated the job on the UI to allow 10 builds until this is updated via the YAML. Anton - please see if this can updated during the week, I belive its the yaml/templates/standard-pipeline.yaml file that needs updating. On Thu, Mar 21, 2019 at 4:39 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Thu, Mar 21, 2019 at 3:59 PM Daniel Belenky (oVirt JIRA) < jira@ovirt-jira.atlassian.net> wrote:
Daniel Belenky commented on OVIRT-2704: ---------------------------------------
AFAIK, this job is limited because it never meant to be used as a production job, but as a way to debug things or specifically run some scenario. Nir, can't your tool work directly with the OST manual job?
We use OST manual job to run OST. But we need to build the artifacts for OST, and the only way this can be done now via the API is using the manual runner.
Please see the entire flow here: https://github.com/nirs/oci/blob/master/system-tests.py
it already allows some concurrency and I guess we could increase it.
Otherwise, I don't have any strict objection on increasing the # of concurrent jobs in the manual runner other than that IMO, it wasn't meant to be used in this scenario and it will be hard to find jobs there.
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) _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W7Z7ANY3PUTUYV...
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5YBEJQ24GAOKVQ...
-- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
participants (3)
-
Daniel Belenky (oVirt JIRA) -
Eyal Edri -
Nir Soffer