[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 <nsof...@redhat.com> wrote:

> On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <d...@redhat.com>
> wrote:
> >
> > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobc...@redhat.com>
> 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/

Reply via email to