[
https://ovirt-jira.atlassian.net/browse/OVIRT-2521?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-2521:
-------------------------------------
{quote}
the bot is running properly now. So I'm just looking for answers on
2 - is there a way to configure this to be on-demand only? in other words,
only run when we invoke 'ci build please'?
{quote}
Not ATM.
{quote}
2a - if not, is there a way to make ovirt ci non-blocking since travis
would still be our source of truth?
{quote}
Yes, I think by default GitHub makes it non-blocking; Its something that you can configure
from the GitHub side.
enable stdci v2 for ovirt-web-ui
--------------------------------
Key: OVIRT-2521
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2521
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Greg Sheremeta
Assignee: infra
Hi,
I want to enable stdci v2 for ovirt-web-ui, to run alongside travis, so we
can easily make rpms from PRs.
I added automation.yaml [1] and updated standard_pipelines [2].
1 - is there anything else I need to do?
2 - is there a way to configure this to be on-demand only? in other words,
only run when we invoke 'ci build please'?
2a - if not, is there a way to make ovirt ci non-blocking since travis
would still be our source of truth?
[1]
https://github.com/oVirt/ovirt-web-ui/pull/794
[2]
https://gerrit.ovirt.org/#/c/94639/1/jobs/confs/projects/standard-pipelin...
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<
https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<
https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100093)