[jenkins] Add otp rpms to build slaves

[Eyal Edri]

> > > > > ----- Original Message -----
> > > > > > From: "Alon Bar-Lev" <alonbl at redhat.com>
> > > > > > To: infra at ovirt.org
> > > > > > Cc: "Eyal Edri" <eedri at redhat.com>
> > > > > > Sent: Monday, November 26, 2012 2:47:16 PM
> > > > > > Subject: [jenkins] Add otp rpms to build slaves
> > > > > > 
> > > > > > Hello,
> > > > > > 
> > > > > > Reminder: I am re-writing the vdsm-bootstrap. It is split
> > > > > > out
> > > > > > to
> > > > > > own
> > > > > > packages ovirt-host-deploy, and otopi.
> > > > > > otopi is common installation framework that may be used by
> > > > > > other
> > > > > > components as well.
> > > > > > 
> > > > > > otopi build job is available at[1].
> > > > > > 
> > > > > > In order to build ovirt-host-deploy rpms in jenkins I need
> > > > > > otopi-devel, otopi-java, otopi to be installed at slaves
> > > > > > machines.
> > > > > > 
> > > > > > These can be acquired from [2].
> > > > > > 
> > > > > > What is the procedure for this?
> > > > > 
> > > > > Long term: this will involve creating a relevant puppet
> > > > > classes
> > > > > and
> > > > > applying it to the jenkins slaves
> > > > > with foreman and puppet master.
> > > > 
> > > > Looking for short term for now...
> > > > 
> > > > > Short term: manual adding these repos to the jenkins slaves,
> > > > > then
> > > > > you
> > > > > can install them via the system job in jenkins.
> > > > > (unless there is an objection on the team, for having custom
> > > > > builds
> > > > > repo on jenkins slaves.. thoughts?)
> > > > 
> > > > What have we done with a package such as vdsm-bootstrap?
> > > > Is it installed? from which repository?
> > > 
> > > it's not, we're not running a bootstrap tests yet, it reuquires a
> > > real host (or nested)
> > > which we don't have yet.
> > 
> > Oh!!! we had no such BuildRequires of any of our components.
> > This is going to change as ovirt-engine will require
> > ovirt-host-deploy-java to build.
> > 
> > > 
> > > > Or ovirt-iso-uploader that is dependency of ovirt-engine?
> > > > I can publish otopi at same repository...
> > > 
> > > we're not installing ovirt-engine yet as well..
> > 
> > Right... this is OK, I am talking about the dependencies.
> > 
> > > 
> > > > 
> > > > > if not, you can open a ticket for it in
> > > > > https://fedorahosted.org/ovirt/report/1.
> > > > 
> > > > If not what? not objection? I will wait.
> > > 
> > > yes, let's wait to hear other team members opinion on this.
> > > 
> > > > 
> > > > Thanks!
> > > > Alon
> > > > 
> 
> Hello People,
> 
> In order to build ovirt-engine-3.2 rpms we will need two packages
> installed on build slaves, these packages are part of our
> development:
>  - otopi
>  - ovirt-host-deploy
> 
> These packages contain jars required as build dependency of
> ovirt-engine.
> 
> The question is how do we want to manage it? The simplest approach is
> to install the required rpm on the build slaves.
> 
> More complex approach may be to use mock to build ovirt-engine rpms.
> 
> What do you think? We need a solution in relative short time.
> 
> Thanks,
> Alon
> 

OK, for the short term, i don't see any harm in adding the nightly repo for fedora 17 slaves so otopi and ovirt-host-deploy can be installed.
we'll add it as a puppet class once our environment is up and running.