[JIRA] (OVIRT-3101) Add "ci system-test" command
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41034#comment-41034 ] Shani Leviim commented on OVIRT-3101: - +1 for adding the suite name. BTW, you can run manually OST with your own parameters (engine artifacts and OST patch set). *Regards,* *Shani Leviim* On Thu, Jun 24, 2021 at 3:08 PM Nir Soffer wrote: > On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David > wrote: > > > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk > wrote: > > > > > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > > triggers OST run. > > > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > > This causes trouble and does not allow non-maintainers to use the > convenient OST > > > > infrastructure. > > > > > > > > Expected flow: > > > > > > > > 1. User add a comment with "ci system-test" > > > "ci system-test" is sooo long, I vote for "ci ost". > > > > +1. > > > > Perhaps we can add an optional suite name? E.g. 'ci ost > ansible-suite-master' > > +1 > ___ > Devel mailing list -- de...@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/de...@ovirt.org/message/SKS3XFCIC6SUPAWV52XMRFQP2CXXLHXG/ > > Add "ci system-test" command > > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/AI4BFZMMZXZ7HYDYYMX5QGRMTGV7FJXU/
[JIRA] (OVIRT-3101) Add "ci system-test" command
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41033#comment-41033 ] Nir Soffer commented on OVIRT-3101: --- On Thu, Jun 24, 2021 at 1:49 PM Marcin Sobczyk wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the > > convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". Works for me, but "system-test" is more consistent with other ci commands: https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_Gerrit/index.html#manual-functionality-of-the-ovirt-ci-system > Add "ci system-test" command > > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7YWOEXG6SHMOWZZHGJ7IDKIV7B422AQU/
[JIRA] (OVIRT-3101) Add "ci system-test" command
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41032#comment-41032 ] Nir Soffer commented on OVIRT-3101: --- On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David wrote: > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk wrote: > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > triggers OST run. > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > This causes trouble and does not allow non-maintainers to use the > > > convenient OST > > > infrastructure. > > > > > > Expected flow: > > > > > > 1. User add a comment with "ci system-test" > > "ci system-test" is sooo long, I vote for "ci ost". > > +1. > > Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' +1 > Add "ci system-test" command > > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/G37YB3WYQGHNMZ5QF53JW6TDI5SQRMLW/
[JIRA] (OVIRT-3101) Add "ci system-test" command
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41031#comment-41031 ] Yedidyah Bar David commented on OVIRT-3101: --- On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the > > convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". +1. Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' Best regards, -- Didi > Add "ci system-test" command > > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5MYXL2F362W6B7NW7TDYGNVIBSIDT2UP/
[JIRA] (OVIRT-3101) Add "ci system-test" command
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41030#comment-41030 ] Marcin Sobczyk commented on OVIRT-3101: --- On 6/23/21 5:44 PM, Nir Soffer wrote: > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > > Expected flow: > > 1. User add a comment with "ci system-test" "ci system-test" is sooo long, I vote for "ci ost". Regards, Marcin > 2. OST flow building and running OST triggered > ___ > Devel mailing list -- de...@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/de...@ovirt.org/message/2FCJZLFJJ2SB3KVQ3YREZBVEYXPBQRUN/ > Add "ci system-test" command > > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Nir Soffer >Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient > OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JQTHIJEUGUP4SKNJX6N25U4JGDUAS2ZX/
[JIRA] (OVIRT-3101) Add "ci system-test" command
Nir Soffer created OVIRT-3101: - Summary: Add "ci system-test" command Key: OVIRT-3101 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to "ci build", "ci test", "ci merge" add a new command that triggers OST run. Running OST is tied now in vdsm (and engine?) to Code-Review: +2. This causes trouble and does not allow non-maintainers to use the convenient OST infrastructure. Expected flow: 1. User add a comment with "ci system-test" 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/A5A2SHSJTW7S4EUD3XWAFX27G3AQXVXZ/
