[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 -- devel@ovirt.org To unsubscribe send an email to devel-leave@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/devel@ovirt.org/message/2FCJZLFJJ2SB3K...
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)