Bug 1282780
Summary: | Add jenkins job to run lago basic sanity on pre releases of ovirt 3.6 | ||
---|---|---|---|
Product: | [Community] ovirt-system-tests | Reporter: | Eyal Edri <eedri> |
Component: | General | Assignee: | Yaniv Kaul <ykaul> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.4 | CC: | bugs |
Target Milestone: | milestone3 | Keywords: | Automation, FutureFeature |
Target Release: | 0.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | ci | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-24 12:39:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | External | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eyal Edri
2015-11-17 12:01:25 UTC
So what you suggest is having some manual triggered job where you can specify the ovirt repository to use? That sounds quite hacky, but seeing that it will take time to automate properly (and some convincing) might be a palliative to the current situation. Changing title and re-phrasing. Now that we see lago runs and works on 3.6 stable repo (i.e 3.6.0 release). Lets clone the job to run on pre releases (i.e 3.6-pre repo), which means we'll test beta/rc's before official releases. this will allow us at this stage (while we don't have yet rpms built per commit - see open bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1279962 Changing assignee, please feel free to re-assign to relevant teams. This is fixed, as we now run the tests on 3.6, 4.0 and master nightlies repos: http://jenkins.ovirt.org/view/oVirt%20system%20tests/ This was verified already as we saw real regression caught with it. In addition, work is being done to run the jobs even more frequent on an 'experimental' repo that will be refreshed every time a new rpm from oVirt is built. you can see more info on jenkins.ovirt.org, for example the deploy job: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_3.6/ and the repos themselves: http://resources.ovirt.org/repos/ovirt/experimental/3.6/latest/rpm/ working and verified in latest Lago: 0.21 |