I think we should maintain a Jenkins repo under
gerrit.ovirt.org.
from my experience in Jenkins code (downstream) it tends to get complex and you always
need more code to the jobs :)
so it's best if we'll keep all jobs configuration (script code) in a git repo.
that way we'll have a backup (which btw, i don't think we have currently for
jenkins.ovirt.org, right?)
Good idea. I don't think we have any backups for jenkins at the moment.
This sounds like a possible solution:
We should be able to push code without a review if we believe its simple and verified.
but also be able to get a review on it if it is long or complex.
what do you think?
e.
----- Original Message -----
> From: "Mike Burns" <mburns(a)redhat.com>
> To: "Eyal Edri" <eedri(a)redhat.com>
> Cc: infra(a)ovirt.org, engine-devel(a)ovirt.org, engine-users(a)ovirt.org
> Sent: Friday, March 16, 2012 10:12:48 PM
> Subject: Re: [Jenkins] Auto Generated ovirt-engine rpms for fedora 16
>
> On Fri, 2012-03-16 at 12:58 -0400, Eyal Edri wrote:
> >
> > ----- Original Message -----
> > > From: "Mike Burns" <mburns(a)redhat.com>
> > > To: "Eyal Edri" <eedri(a)redhat.com>
> > > Cc: "Doron Fediuck" <dfediuck(a)redhat.com>,
> > > engine-devel(a)ovirt.org, engine-users(a)ovirt.org, infra(a)ovirt.org
> > > Sent: Friday, March 16, 2012 4:45:20 PM
> > > Subject: Re: [Jenkins] Auto Generated ovirt-engine rpms for
> > > fedora 16
> > >
> > > On Thu, 2012-03-15 at 03:24 -0400, Eyal Edri wrote:
> > > > already exists :)
> > > >
> > > >
http://jenkins.ovirt.org/view/vdsm/job/vdsm_create_rpms/
> > >
> > > I was looking at this and noticed that it picked up
> > > ovirt-node-iso
> > > rpms
> > > in the build artifacts as well. When I looked into why, I found
> > > that
> > > it's building the rpms in ~jenkins/rpmbuild. This can be easily
> > > changed
> > > by exporting the HOME variable. I'll make the changes if people
> > > ACK,
> > > but otherwise I won't since I'm not the vdsm maintainer.
> > >
> >
> > Mike,
> > i created that job, so if it's changes in the job configuration you
> > can go a head and make the change.
> >
> > Eyal.
>
> Done, though it took a bit more than it should have. jenkins really
> messes things up when you try to run git describe...
>
> It should work now though.
>
> Mike
>
> >
> > > Mike
> > >
> > > Diff:
> > >
> > > -#git clone
git://gerrit.ovirt.org/vdsm vdsm-git
> > > -
> > > #create VDSM rpms
> > > -cd vdsm-git
> > > +export HOME=${WORKSPACE}
> > > make clean
> > > ./autogen.sh --system
> > > ./configure
> > > make rpm
> > >
> > > -cd $WORKSPACE
> > > -rm -rf rpmbuild
> > > -mv ~/rpmbuild .
> > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Doron Fediuck" <dfediuck(a)redhat.com>
> > > > > To: "Eyal Edri" <eedri(a)redhat.com>
> > > > > Cc: engine-users(a)ovirt.org, engine-devel(a)ovirt.org,
> > > > > infra(a)ovirt.org
> > > > > Sent: Wednesday, March 14, 2012 11:30:40 PM
> > > > > Subject: Re: [Jenkins] Auto Generated ovirt-engine rpms for
> > > > > fedora 16
> > > > >
> > > > > Cool!
> > > > >
> > > > > Any chance to have the same with vdsm rpm's?
> > > > >
> > > > > On 14/03/12 22:45, Eyal Edri wrote:
> > > > > > fyi,
> > > > > >
> > > > > > a new Jenkins job has been added to
jenkins.ovirt.org.
> > > > > >
> > > > > > you can now d/l fresh ovirt-engine rpms after each commit.
> > > > > >
> > > > > > the rpms are created and latest are stored here:
> > > > > >
> > > > > >
http://jenkins.ovirt.org/view/ovirt_engine/job/ovirt_engine_create_rpms/
> > > > > >
> > > > > > the job will also notify the author in case his/her commit
> > > > > > will
> > > > > > break the rpm build.
> > > > > >
> > > > > > latest rpms for now:
> > > > > >
> > > > > > ovirt-engine-3.1.0_0001-1.8.fc16.src.rpm
> > > > > > ovirt-engine-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-backend-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-config-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-dbscripts-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-debuginfo-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-genericapi-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-image-uploader-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-iso-uploader-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-jboss-deps-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-log-collector-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > >
ovirt-engine-notification-service-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-restapi-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-setup-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-tools-common-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > > ovirt-engine-userportal-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > >
ovirt-engine-webadmin-portal-3.1.0_0001-1.8.fc16.x86_64.rpm
> > > > > >
> > > > > > Enjoy,
> > > > > > Eyal Edri
> > > > > > oVirt Infra Team
> > > > > >
> > > > > > _______________________________________________
> > > > > > Infra mailing list
> > > > > > Infra(a)ovirt.org
> > > > > >
http://lists.ovirt.org/mailman/listinfo/infra
> > > > >
> > > > >
> > > > _______________________________________________
> > > > Infra mailing list
> > > > Infra(a)ovirt.org
> > > >
http://lists.ovirt.org/mailman/listinfo/infra
> > >
> > >
> > >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> >
http://lists.ovirt.org/mailman/listinfo/infra
>
>
>