Run jenkins test on a rhel6 host

[Eyal Edri]

----- Original Message -----
> From: "Eyal Edri" <eedri at redhat.com>
> To: "Itamar Heim" <iheim at redhat.com>
> Cc: infra at ovirt.org
> Sent: Monday, January 21, 2013 9:46:36 AM
> Subject: Re: Run jenkins test on a rhel6 host
> 
> 
> 
> ----- Original Message -----
> > From: "Itamar Heim" <iheim at redhat.com>
> > To: "Karsten 'quaid' Wade" <kwade at redhat.com>
> > Cc: infra at ovirt.org
> > Sent: Monday, January 21, 2013 6:54:09 AM
> > Subject: Re: Run jenkins test on a rhel6 host
> > 
> > On 01/20/2013 01:09 PM, Karsten 'quaid' Wade wrote:
> > > On 01/20/2013 06:34 AM, Dan Kenigsberg wrote:
> > >> On Thu, Jan 17, 2013 at 03:58:55PM +0800, Mark Wu wrote:
> > >>> Hi guys,
> > >>>
> > >>> I am a vdsm developer.  Recently I submit a vdsm patch fix a
> > >>> break
> > >>> on fedora 18. I just verify it on fedora, but not on RHEL6
> > >>> before
> > >>> merged. Unfortunately, my patch called a function which
> > >>> has a bug on rhel6. That bug was fixed in fedora, but not
> > >>> backported
> > >>> to rhel6.  So I am thinking is it possible to also run the
> > >>> jenkins
> > >>> test on a rhel6 host for each patch? Then we can find the break
> > >>> in
> > >>> time.
> > >>> and the developer don't need to run the test cases on two
> > >>> systems
> > >>> for one patch.
> > >>
> > >> I'd like to join Mark's plea.  I believe that the only problem
> > >> is
> > >> of finding
> > >> the resources for another Jenkins slave.
> > >>
> > >> Missing an el6 slave is a pain point for me - I've
> > >> accepted Saggi's http://gerrit.ovirt.org/9986 and now Vdsm's
> > >> master
> > >> branch fails to build on EL6 on the following grounds:


what job runs currently per patch for vdsm that will verify this patch,
and you want it running on EL?

> > >
> > > OK, we're working on getting actual RHEL 6 entitlements for the
> > > new
> > > hosts at Rackspace, which has one server to be dedicated to
> > > multiple
> > > Jenkins slaves.
> > >
> > > It will be a week or more for those hosts to be available. Once I
> > > have
> > > the details, I'll forward them to the Jenkins admins so they can
> > > get
> > > started ASAP. (We don't need to wait for Puppet, we can puppetize
> > > the
> > > server later.)
> > >
> > > - Karsten
> > >
> > >
> > >
> > > _______________________________________________
> > > Infra mailing list
> > > Infra at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> > >
> > 
> > we have two rhel 6 jenkins slaves on ec2 today - is there an issue
> > with
> > them?
> 
> they are running 6.2, is that enough?
> can we upgrade them to 6.3?
> 
> i can run the same job on them if it will help for now.
> 
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> > 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>