Hello,
We recently noticed that configure-mirrors enables deb-src repositories on Debian but not Ubuntu. Typically deb-src repositories are not required by CI systems as jobs don't need those packages. These packages do consume significant disk space on your mirrors and the current configure-mirrors behavior means that you must replicate and include these package repos.
We would like this to no longer be the case so we've pushed a change to enable deb-src behind a configure-mirrors option [0]. Currently this flag defaults to True to preserve the preexisting behavior. In two weeks we will flip the default to False [1] improving the situation for people running the CI system and its package mirrors. If jobs need the source packages they can toggle the flag in their jobs or manually configure deb-src repo configuration themselves.
[0] https://review.opendev.org/c/zuul/zuul-jobs/+/839592/
[1] https://review.opendev.org/c/zuul/zuul-jobs/+/839593/
Clark
The Zuul team is pleased to announce the release of Zuul 5.2.5.
Download it from PyPI: https://pypi.org/project/zuul
Find container images at: https://hub.docker.com/u/zuul
The release notes for 5.2.3 through 5.2.5, included below, are also
available in the documentation with hyperlink references:
https://zuul-ci.org/docs/zuul/5.2.5/releasenotes.html
Bug Fixes
=========
* Projects and jobs on branches whose names have special characters in
regular expressions could fail to match changes as intended. Implied
branch matchers automatically generated from branch names are now
treated as requiring exact matches. Any user-specified branch matcher
(including in job.branches and pragma.implied-branches) are still
treated as regular expressions.
* Project name regex handling has been updated to return all possible
matches. Previously if there were collisions with short names it was an
error. The point of the regex system is to simplify configuration and
apply configs to all projects that match. Collisions don’t impact this
behavior so we don’t need to raise an error in these cases.
* A change in 5.2.3 began reporting NO_JOBS results to the database
which was unintentional. This has been corrected and they are no longer
recorded in the database.
* Further instances of reporting NO_JOBS results to the database when
not necessary have been corrected.