Excerpts from Dejan Muhamedagic's message of 2012-09-19 07:29:21 -0700: > On Tue, Sep 18, 2012 at 03:10:45PM -0600, Alan Robertson wrote: > > On 09/18/2012 01:44 PM, Clint Byrum wrote: > > > Excerpts from Alan Robertson's message of 2012-09-17 12:23:29 -0700: > > >> On 09/17/2012 01:05 PM, Dejan Muhamedagic wrote: > > >>> Hi Alan, > > >>> > > >>> On Mon, Sep 17, 2012 at 10:28:52AM -0600, Alan Robertson wrote: > > >>>> I still need to get it working for RHEL 6.2 - and for that matter, > > >>>> probably on RHEL5. But feel free to try it on newer OSes. There is > > >>>> another known issue with these older versions of glib - and I know we > > >>>> need to get it going. > > >>>> > > >>>> But, if you add the -Werror flag, you'll run into one other issue, > > >>>> which > > >>>> I also know the workaround for. > > >>> Did you consider using the opensuse build service? It supports a > > >>> number of different platforms and it has been working quite well > > >>> for some time. https://build.opensuse.org/ > > >>> > > >> I did think about it. The last time I looked at it I couldn't make > > >> sense of how to use it. Do you want to tackle that for us? > > >> > > >> I think that makes more sense than trying to replicate all the platforms > > >> it compiles for. > > >> > > > I have 0 experience with suse's build service, so thats fine but it will > > > take me a lot longer to get it up than a simple jenkins instance, which I > > > had up and ready to build debs before I hit send on my last email. > > > > > > Will poke at it a bit now though. > > Let Dejan and me know what you need from us. Dejan's a great guy. > > > > But having someone else supply all the horsepower and the build > > environments hopefully will work out - given that the nanoprobes ideally > > would run everywhere. I think the build service will also cover some of > > the BSDs too... > > No, no BSD yet. > > For Linux distributions we need a spec file and a deb rules file > (not sure what else debian requires). I'm not that experienced > when it comes to writing specfiles though.
I've got some preliminary things building on the service. It feels fairly opaque and weird, but I was sort of able to get rpms and debs out of it. Honestly, its interesting but its not really a CI system that will be helpful to developers in solving problems it finds. I agree that horsepower is a problem, so maybe its worth it to tap into open build for that. However, to me the CI system should: * Gate trunk * Build on all targets * Run the test suite on all targets One thing to do to get horsepower is to tap into the community and just ask for machines/VMs running any platform they'd like to see supported. That worked fairly well for Drizzle, which has always had a ton of build targets. _______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring [email protected] http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
