[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&focusedCommentId=41032#comment-41032 ] Nir Soffer commented on OVIRT-3101: ----------------------------------- On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk@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
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)
participants (1)
-
Nir Soffer (oVirt JIRA)