fedora 18 builds on jenkins.ovirt.org
Alon Bar-Lev
alonbl at redhat.com
Thu Nov 29 07:57:20 UTC 2012
----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Eyal Edri" <eedri at redhat.com>
> Cc: "infra" <infra at ovirt.org>, "Moran Goldboim" <mgoldboi at redhat.com>, "Dan Kenigsberg" <danken at redhat.com>, "Alon
> Bar-Lev" <alonbl at redhat.com>
> Sent: Thursday, November 29, 2012 9:53:28 AM
> Subject: Re: fedora 18 builds on jenkins.ovirt.org
>
> On 11/29/2012 02:08 AM, Eyal Edri wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Itamar Heim" <iheim at redhat.com>
> >> To: "Eyal Edri" <eedri at redhat.com>
> >> Cc: "infra" <infra at ovirt.org>, "Moran Goldboim"
> >> <mgoldboi at redhat.com>
> >> Sent: Thursday, November 29, 2012 2:26:21 AM
> >> Subject: Re: fedora 18 builds on jenkins.ovirt.org
> >>
> >> On 11/28/2012 02:02 PM, Eyal Edri wrote:
> >>> fyi,
> >>>
> >>> i've done some changes to allow f18 builds:
> >>>
> >>> 1. upgraded fedora17-slave-vm01 to fedora18-slave-vm01. (new
> >>> label
> >>> fedora18)
> >>> 2. created new matrix jobs [1] to create rpms per project for
> >>> each
> >>> operating system,
> >>> so only one job will create rpms for all operating systems
> >>> (currently f17,f18).
> >>> 3. publish rpms job will copy all artifacts from the matrix jobs
> >>> into sub-folder on ovirt.org.
> >>> 4. we need to update publish script that runs on ovirt.org to
> >>> take
> >>> fedora 18 files as well.
> >>>
> >>> so far i've created the following matrix jobs:
> >>>
> >>> http://jenkins.ovirt.org/view/rpms/job/ovirt-host-deploy_create_rpms_fedora/
> >>> http://jenkins.ovirt.org/view/rpms/job/otopi_create_rpms_fedora/
> >>> http://jenkins.ovirt.org/view/rpms/job/ovirt-engine_create_rpms_fedora/
> >>>
> >>> let me know when the publish cronjob on linode is updated, so
> >>> i'll
> >>> create the projects for other jobs also.
> >>>
> >>> example f18 rpms:
> >>>
> >>> http://jenkins.ovirt.org/view/rpms/job/ovirt-engine_create_rpms_fedora/jdk=java-1.7.0-openjdk.x86_64,label=fedora18/
> >>>
> >>> [1]
> >>> http://jenkins.ovirt.org/view/rpms/job/ovirt-host-deploy_create_rpms_fedora/
> >>>
> >>>
> >>> Eyal.
> >>>
> >>
> >> where are they published under http://www.ovirt.org/releases?
> >>
> >
> > OK, just found the cronjob that fetch them and creates the repos.
> > i updated it to take f18 as well (didn't know what to do with
> > ovirt-release:
> >
> > /bin/find /home/jenkins/ovirt-nightly/artifacts/ -name
> > "*ovirt-release-fedora-*" -exec mv {}
> > /var/www/html/releases/nightly/rpm/Fedora/17/noarch \;
> >
> > it doesn't have a distinguish naming per fedora rel...
> >
> > publish script is running now, we should have f18 rpms soon on
> > ovirt.org/releases/nightly/rpm/Fedora/18
> >
> >>
>
> thanks.
> can you please chase all relevant package owner for versions to
> change
> to 3.2?
> danken - is there a reason all the hooks are in the noarch, but vdsm
> is
> in the x86_64?
http://gerrit.ovirt.org/#/c/6098/
> alon - which version scheme for otopi and ovirt-host-deploy.
> easier to track if it matches ovirt version scheme for now (for sure
> for
> o-h-d).
major - ok.
minor - I am not so sure... as as soon as 3.3 out I am unsure we will sync.
Fix should not match.
bottom line I don't think we should artificial sync versions...
Alon.
More information about the Infra
mailing list