[Piuparts-devel] testing more architectures with piuparts

Paul Wise pabs at debian.org
Sun Mar 19 01:30:05 UTC 2017

On Sun, Mar 19, 2017 at 5:41 AM, Holger Levsen wrote:

> However, I realized today, that there is a cheap way out:
> - rename piuparts.d.o to amd64.piuparts.d.o
> - point piuparts.d.o at somewhere sensible (on amd64.piu….d.o)

We would need to make sure that this part doesn't break all the
services that use it or link to it. That appears to be at minimum,
release.d.o, UDD, PTS/tracker, DDPO and jenkins.

> i386 was taken as an example here for any other arch, though i386 is at least
> interesting because we still have some i386 only packages in the archive and
> because i386 still has a bigger user base than most other archs.

i386 is probably easier on the hardware side too.

> Alternativly we could also make use of just a single non-amd64 slave and test
> on that using a more hackish implementation, namely introducing "sid-i386" and
> only test that on i386 and hack that into the amd64 webpages.

Sounds ick indeed.

> And In both cases the longterm goal would be to have a single master host
> eventually, it's just that we think the detour via multiple masters would
> result in better results faster…

Fair enough.



More information about the Piuparts-devel mailing list