On 07/12/2012 11:48 AM, Mike Burns wrote:
On Thu, 2012-07-12 at 10:59 -0400, Eyal Edri wrote:
----- Original Message -----
From: "Robert Middleswarth" <[email protected]>
To: "infra" <[email protected]>
Sent: Thursday, July 12, 2012 5:44:44 PM
Subject: Jenkins and RHEL 6.2

I see there are 2 RHEL 6.2 slaves added to Jenkins and I see they are
doing something with the engine?  What are they actually doing since
I
don't see any artifacts left over?  How hard would it be to tweak the
existing ones to create .rpms?

currently they are used for running mvn jobs like unit tests/find bugs.

you mean use them to create RPMs for ovirt-engine?
supposing make rpm will work for that, all we'll need is to make sure they have
the right rpm build packages installed (rpmbuild, make,autoconf,etc....)
If we want to do that, we should go down a slightly different path.
Each project should have a job that makes the source rpm and tarball.
Then separate jobs on each of the platforms (fedora, RHEL, ubuntu,
etc...) that will take the srpm and/or tarball and generate packages for
the distro.

Mike
Well all the packages are built from a tar file but SPRM wont work for Debian based systems. On my testing system creating the .tar.gz file takes like 10 seconds. But having an updated tar.gz file on every master commit could be useful. Not sure how much having a pre-done src tar is going to save in actual build time. Although having diff build packages for each distro makes a lot of since. I am all about steps to make something happen. I can think of some steps we could go though to convert the process but at best it would be based on my basic knowledge you know the current build process and would be best for you to outline the steps to get the changes in place. What steps do you think are the best steps to getting the process changed up?

Thanks
Robert

Thanks
Robert
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra

_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra



_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to