[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23817#comment-23817 ] Yedidyah Bar David commented on OVIRT-903: ------------------------------------------ On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi

master-to-master CI upgrade tests ---------------------------------

Key: OVIRT-903 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra

Hi all, Recently a patch to the engine [1] added a new package, with a certain set of dependencies, which broke upgrade. This is similar to [2] but for a new package. CI wasn't affected, I think because of [3]. To make CI test such flows, we should have a job that: 1. Builds, installs and sets up the version we want to test 2. Pushes a dummy change to the local git repo (to force a new version), build the patched tree, create a yum repo with the build and add it to yum.repos.d. 3. yum update 4. engine-setup Another option is to revert [3], or to duplicate - have both "upgrade current to self" and "upgrade latest snapshot to current". The downside is that it will be checked later than above plan - instead of in the same build, will only be tested in the first build that uses the snapshot after it was updated, and also will be misleading, as the reason why that job failed will not be apparent (which was why [3] was added). Please handle. I can of course try to help. Best, [1] https://gerrit.ovirt.org/66999 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 [3] https://gerrit.ovirt.org/67263 -- Didi

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