[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: The CI issue (was Re: Request push access on Salsa)



Aloïs Micard <creekorful@debian.org>,
18/10/2021 – 18:33:14 (+0200):

> Since we try to keep only one version of a package at a given time,
> every package upload may break other packages that depends on it. This
> is especially true for Go core package.
> 
> While we could use a standards workflow and use tools like
> dose-ceve(1) to fetch reverse depends of a Go package and rebuild
> everything in a clean schroot to make sure nothing has been broke with
> the update, it is much more faster to keep a local index of all Go
> packages and rebuild the whole Go archive and check for breakage.
> That's why we have such a 'special' setup. Because it allows us to do
> efficient rebuild (<30sec to rebuild the whole Go archive with an
> up-to-date cache). We sacrifice the easier common setup for
> performance.

Thanks for the detailed explanation! As said earlier, I believe that a
(very) fast CI is key and justify spending time on engineering it well.

-- 
Faustin

Attachment: signature.asc
Description: PGP signature


Reply to: