<html><body>
<p><tt><font size="2">Francois Dion <francois.dion@gmail.com> wrote on 09/04/2012 07:29:09 PM:<br>
> <br>
> On Tue, Sep 4, 2012 at 5:38 PM, Nick Zivkovic <zivkovic.nick@gmail.com> wrote:<br>
> >>> 2) document every single IPS failure and either fix the<br>
> >>> packages or the IPS code (depend on what caused the failure), and<br>
> >><br>
> >> First thought here is that it needs to be in the bug tracker, but that may<br>
> >> not be easily accessible either. Maybe a sub-page on the wiki?<br>
> ><br>
> > Either should be fine. FreeBSD records their ports build failures on<br>
> > their wiki. I think Gentoo recorded this on a bug tracker. Wiki is<br>
> > probably easiest.<br>
> <br>
> Jenkins can automate all of that. For $JOB, I manage various products,<br>
> millions of lines of code in total with it. The nice thing is that it<br>
> will "blame" whoever breaks the build. It also provides an easy to<br>
> read dashboard, and notify only on status change, not on every build<br>
> that fails etc. Plus it can post to a URL, so a few lines of python<br>
> code with web.py and you have an interface to a wiki or bug tracker.<br>
> <br>
> Francois<br>
> <br>
</font></tt><br>
<tt><font size="2">I spent some time thinking about this today, and you are right.</font></tt><br>
<br>
<tt><font size="2">A Jenkins server which with a plugin to publish via IPS to a sandbox server (or use the build system's IPS publishing, where available), and one to make a zone on the build server to work in would not only do everything I want, but exceed it. I guess what I care about is less the build system, and more psudo-CI.</font></tt><br>
<br>
<tt><font size="2">I would also need a way to promote builds, once working (and again once tested, sandbox->testing->stable, which means I really don't care much about blame. This worked well for SJ). I think I'll fire up a couple of VMs and get this working. </font></tt><br>
<br>
<tt><font size="2">I have used Jenkins before, it's really an awesome bit of software. For the life of me I don't know why I didn't realize Kohsuke Kawaguchi had already done most of the work to make me happy again! Guess I just got myself stuck in the mindset that we have too many build systems and didn't realize that that isn't what I am really frustrated by at all.</font></tt><br>
<br>
<br>
<br>
<tt><font size="2">That said, I think what Nick was talking about was not a build failure, but common issues IPS itself can have. I've seen a few (rare) times where it will just spit out a call-stack. Haveing a goto page of potental problems and fixes/workarounds would help.</font></tt><br>
<br>
<br>
<font size="2" face="sans-serif">Andrew Hettinger<br>
<a href="http://Prominic.NET">http://Prominic.NET</a> || AHettinger@Prominic.NET<br>
Tel: 866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l) <br>
Fax: 866.372.3356 (toll free) -or- +1.217.356.3356 (int'l)</font></body></html>