Axel.Thimm at ATrpms
Apr 1, 2009, 11:02 AM
Post #2 of 2
(482 views)
Permalink
|
On Wed, Apr 01, 2009 at 09:31:52AM -0700, Scott Harris wrote:
> Howdy all,
> I was curious if you were willing to share how
> you've automated building multiple releases for multiple
> OSes? Where I work we are trying to support releases for
> all derivations of RedHat from 3 through 5 Update 3.
That's more an atrpms-devel type question, but anyway: Like any other
buildsystem out there I use chroots to capture environments for the
various supported distribution. These chroots were once managed by
apt, but since apt has broken on Fedora 10/11 sometimes I switched to
a combination of yum and smart (unfortunately yum alone does not have
a feature like yum install foo-the.version.I.want).
There are several tools for working with chroots, the most prominent
ones are mock and koji as a high level supervisor, but I still use a
couple of simple shell scripts.
> Right now if we move to a new version of RedHat that is
> substantially different, say from RH3 to RH5, we manually
> recompile all the dependent RPMs we need with rpmbuild.
> This takes one person quite a bit of time. What's the b
> best approach to automation?
I use a for loop over all projects. I just need to add a distribution
and then let the servers work out on it. It takes quite some time to
rebuild everything, but there is no human supervision needed (or very
little, only when something breaks from distro X to X+1).
--
Axel.Thimm at ATrpms.net
|
