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...
With that as the current setup, I'd like to use Jenkins for a couple different things, the primary "thing" being an automated build management framework that I can monitor remotely and distribute, if so desired. The secondary "thing" would be to make use of more features and plugins offered by Jenkins that seemingly are only used by Java apps. Since I'm just starting the design phase of this project, looking at how others have setup their GCC/C-based Jenkins will be helpful. The OpenSUSE instance of Jenkins may be a good starting point: http://ci.opensuse.org/ Cheers. - CB On Thursday, May 17, 2012 5:57:45 PM UTC-7, LesMikesell wrote: > > On Thu, May 17, 2012 at 5:41 PM, Christian Bryant > <[email protected]> wrote: > > I'm in the process of moving my Linux From Scratch build system to be > > managed by Jenkins (I can check up on the build using a Jenkins Android > > app). However, I'm stumbling through examples of non-Java build > > configuration scripts that some folks have put out there for GCC and > Linux > > kernel builds. Anyone in the group built a build management framework > for a > > GNU/Linux OS like Linux From Scratch? From the Jenkins kernel build > code > > below (not mine), I can see that I'm going to have a large number of > shell > > tasks since I'm going to be building (on top of LFS 7.1) a large number > > (~200) of packages in addition to the kernel, and squirting out an ISO > from > > this (for a Live DVD). Appreciate any pointers from the local SMEs. > > Cheers. > > Jenkins can run whatever build script you were using before. Do you > want to break out each package as a separate job so they can build in > parallel or as changes show up? Is the source in some source control > system that jenkins can poll? > > -- > Les Mikesell > [email protected] >
