On Fri, May 18, 2012 at 1:04 AM, Christian Bryant
<christian.bry...@ucla.edu> wrote:
> Not sure if you're familiar with LFS (http://www.linuxfromscratch.org/) but
> there are a variety of ways to build the OS. I chose jhalfs
> (http://www.linuxfromscratch.org/alfs/) which "reaches" into the LFS book
> source XML files to generate make files. It does, however, require quite a
> bit of hand-holding, editing and trial-error. It would make sense to build
> each package, including the kernel, as a separate job, with a final job
> representing the final integration of the temporary system with the app
> packages, then applying the bootscripts. The final result ultimately should
> be an ISO of a Live system, so perhaps that is the final job...
I don't know enough about it to offer specific advice, but basically
you want to think about what should trigger a build. Does each
package update independently somewhere that jenkins can check? Then
have separate jobs for each action that can proceed independently so
you have the option of distributing them. The build results either
have to be archived on the master or the build scripts have to publish
them somewhere that the iso building step can find. You'll need some
versioning concept for this output to allow building updates to happen
currently with generating the last complete iso.
--
Les Mikesell
lesmikes...@gmail.com
