[JIRA] (OVIRT-627) Implement Zuul as pre-merge action to run experimental flows

[eyal edri [Administrator] (oVirt JIRA)]

     [ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

eyal edri [Administrator] reassigned OVIRT-627:
-----------------------------------------------

    Assignee: bkorren  (was: infra)

I guess this is the second step after we see Zuul integration works.

I think the 1st thing we should do is create some sort of design diagram of how we want the flow to work and what input/output/triggers it should have.

> Implement Zuul as pre-merge action to run experimental flows 
> -------------------------------------------------------------
>
>                 Key: OVIRT-627
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-627
>             Project: oVirt - virtualization made easy
>          Issue Type: Bug
>            Reporter: eyal edri [Administrator]
>            Assignee: bkorren
>
> Today, we can test a patch per project on each of the ovirt versions using experimanal flow
> i,e:
> run build_artifacts with a patch -> deploy to experimental -> run test job
> this is problematic since it actually deploys the build with the patch to the experimental repo which should only contain built pkg that are merged.
> We need to either close the flow or add param to the build artifacts that says 'create temp repo/test repo' so the built rpm won't be part of the official tested repo and the link to latest_tested won't be updated if this option is triggered.



--
This message was sent by Atlassian JIRA
(v1000.606.0#100023)