[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-422:
--------------------------------------------
    Status: Accepted  (was: New)

[~fabiand at redhat.com][~sbonazzola at redhat.com]
I believe you made some progress for this flow, including adjusting the rhevh and appliance jobs plus adding links + release rpm.

Can you add some info & links so we'll be able to plan the remaining items to finish the automation of the flow?

> Create jenkins job to compose ovirt 4.0 snaphost early builds
> -------------------------------------------------------------
>
>                 Key: OVIRT-422
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422
>             Project: oVirt - virtualization made easy
>          Issue Type: Task
>          Components: Jenkins, repoman
>            Reporter: eyal edri [Administrator]
>            Assignee: infra
>            Priority: Highest
>
> We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build.
> * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on  
>    resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/
> * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1]
> * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1
> * We'll run repoclosure on it once the copy is finished
> * run sanity (either manually or via Lago manual if possible)
> * rhevh team run sanity on the node builds from nightly 
> * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link.
> * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg.
> * Send email to users/devel with info on release (list of bugs + link to release rpm).
> [2] cat ovirt-4.0-snapshots.repoman (the conf file)
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest



--
This message was sent by Atlassian JIRA
(v7.2.0-OD-03-014#72000)