[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900#comment-13900 ] eyal edri [Administrator] commented on OVIRT-422: ------------------------------------------------- Last update on needed steps: Current status: "Stage 1" (first snapshot repo without images) * a. oVirt nightlies are being published as usual * b. A snapshot was created manually using repoman command, as described in [1] * c ** missing ** * d. new release rpm for 4.0 was created manually [2] * e ** missing ** * f. new softlink was created for latest pre-alpha releases [3] "Stage 2" (final repo with images) * a. new jobs [4] building node + appliance created using the rpm from [3] Missing steps: "Stage 1" (first snapshot repo without images) * new jenkins job that will run the whole flow starting from 1b, work has started here [5] (@sandro, please correct if i'm wrong) * new step for checking repoclosure needs to be added as step 'c', code can be taken from [6]. * automate the step of building the release rpm pointing to a specific release dir. * create new release rpm that will always point to latest snapshot link [3] * add sanity for first repo using lago, similar to [7], just using the new release rpm to run on the new snapshot (step 1e) "Stage 2" (repo including images) * run the job(s) to build appliance, node & ovirt-live using the rpm from [2]. (job for ovirt-live might needs fixing to use release rpm) * push the new images to the new repo, using TBD job * run repoclosure to make sure images are install-able, similar to [6] * run lago sanity tests on whatever is possible (node/appliance/he) * update softlink [3] to point to new repo with images * make repo readonly * move bugs to ON_QA [8] * send email on release with links + changelog [1] https://ovirt-jira.atlassian.net/browse/OVIRT-422 [2] http://resources.ovirt.org/pub/ovirt-4.0_prealpha2/rpm/el7/noarch/ovirt-rele... [3] http://resources.ovirt.org/pub/ovirt-4.0_prealpha-latest/ [4] [~fabiand@redhat.com] - can you share the links to the jobs? [5] https://gerrit.ovirt.org/#/c/54626/ [6] http://jenkins.ovirt.org/job/repos_master_check-closure_merged/ [7] http://jenkins.ovirt.org/job/ovirt_master_system-tests/ [8] as first step we'll use the logic of extracting bugs from the commits msg for a list of projects (do we need approval from each maintainer?)
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)