Hi, as you might have seen, I'm running certain d-i jobs on http://jenkins.debian.net/
There are three views showing d-i related jobs, which are http://jenkins.debian.net/view/d-i_packages/ http://jenkins.debian.net/view/d-i_manual/ http://jenkins.debian.net/view/d-i_misc/ In these views 4 kinds of jobs are shown and run: d_i_build_* - there is one job for each git repo referred to in http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co Each job pdebuilds the master branch of its git repo on every git push in a sid environment. d_i_manual - builds the full installation-guide package with pdebuild in sid on every commit to svn://svn.debian.org/svn/d-i/ matching these patterns: /trunk/manual/debian/.*, /trunk/manual/po/.*, /trunk/manual/doc/.* /trunk/manual/scripts/.* d_i_manual_* - builds a language (on wheezy) on every commit of svn/trunk/manual/$LANG with "make languages=$LANG architectures=amd64 formats=html" d_i_parse_build_logs - parses logs from http://d-i.debian.org/daily- images/build-logs.html daily, to give them a bit more exposure. IMHO this is just more or less a demo what could be done, as I'm quite aware that these are not really optimal jobs to support d-i development - which is my motivation to do this :-) So you need to tell me more what you need, or what is sensible. http://jenkins.debian.net/userContent/about.html has a general description of the setup. Stuff I already know is missing: * svn/trunk/packages - I have no idea what to build here, but I see frequent commits. Can you help? * notifications - while jenkins does nice email notifications by default (it sends mail on every failure and when a build succeeds, it informs once and then it shuts up til the next failure), I think it's better to start with IRC notifications in #debian-boot - what do you think? * testing actuall installations with d-i, for that I plan to give http://www.os-autoinst.org/ a try * bubulle already wrote: 'Another interesting target would be d-i builds including non uploaded packages (something like "d-i from git repositories" images). That would in some way require to create a quite specific image, with all udebs (while netboot only has udebs needed before one gets a working network setup).' - as you can see I'm going in that direction, but I'm not there yet. Feedback very much welcome. I'll reply to this mail myself too, to keep this mail somehwat short, but I still want to explain the current build failures... (and ask & give ideas how to deal with them.) cheers, Holger -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211171147.51179.hol...@layer-acht.org
