>mar. 07 oct. 2025 at 10:35, Maxim Cournoyer <[email protected]> wrote:
> Hi Cayetano, > > Cayetano Santos <[email protected]> writes: > >>>lun. 06 oct. 2025 at 15:30, Andreas Enge <[email protected]> wrote: >> >>> That sounds like a lot, but with "guix package -A | wc" showing 29351 >>> packages altogether, this means that about 1300 packages currently >>> do not build. So we are very far from getting to zero build failures. >> >> Do we have a means to be advertised when a set of packages fails to build ? >> >> Say emacs-team needs to monitor the packages they take care of. When >> something fails, an email is sent somewhere (or atom feed, whatever) so >> that, at a minimum, one knows there is something wrong is going on. > > You can follow the RSS stream of CI and watch for new breakage > there. There's some info in our doc that says how this can be setup in > e.g. Gnus, see (info "(guix) Cuirass Build Notifications"). So we have ci.guix.gnu.org/events/rss/?specification=master ass rss feed to get notifications about branches, this is already something, thanks ! > More drastically, you could have a manifest to build all the packages on > demand (many teams already have such a manifest) or even add them to > your user profile to notice. Under etc/teams, I see. Do we have somewhere an example manifest which includes a list of modules to build ? This would help to build all of a team packages using sr.ht ci [0], for example. > All of these options are still subpar compared to a proper CI system > that would gate the breakage before it gets merged to the live branch, > so thanks to Ludovic, Romain and others who have been working toward > improving things on this front. Absolutely. The cuirass bot is of great help to that respect. C. [0] https://man.sr.ht/~whereiseveryone/builds.sr.ht-guix-cookbook/
signature.asc
Description: PGP signature
