Re: building and testing d-i with jenkins

[Holger Levsen <holger@layer-acht.org>]

Hi Joey,

On Samstag, 17. November 2012, Joey Hess wrote:
> You forgot to mention http://jenkins.debian.net/view/chroot-tests/ which
> all test debootstrap and task installs.

Right, thanks, these are indeed relevant for this list.
 
> Of traslations to packages/po, presumably. Since these are in turn
> exploded out to the translations of individual packages that you already
> test, I don't think additional tests are needed here.

is that an immediate automated process or would it help if jenkins would test 
this on each commit?
 
> If IRC notifications tend to come shortly after commit notifications, I
> think using IRC makes sense.

I'll switch the repo urls jenkins is using from git+svn to http and squid and 
see how much traffic/load 2min polling causes...  (currently its 30min for d-
i_manual* and 6min for d-i_build)

The other option are scm hooks with active notification, but I'd like to avoid 
this. (As I plan to monitor more repos in future...)
 
> I'd like to see debootstrap failure notifications sent to debian-devel,
> or someplace like that. It can be caused by breakage in a great many
> packages, and getting Debian as a whole to own keeping debootstap and
> task installs working would take some load off of d-i.

/me nods, I will bring this up there.
 
> Thanks for your work.  Very much appreciated.

Thanks!


cheers,
	Holger