On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <[email protected]> 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 _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/UIZOOEASMPUE3VWDNNPN23VI64YJ5EIA/
