-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On June 5, 2016 9:04:26 AM PDT, "Michał Górny" <mgo...@gentoo.org> wrote: >Hello, everyone. > >I have the pleasure to announce that a few improvements have been >deployed by the Repository mirror & CI project today. > > >1. The mirror for 'gentoo' repository [1] now has a default 'stable' >branch. It is updated automatically by the gentoo-ci checker, >and therefore always contains the latest repository state that has been >confirmed 'green' by CI. While this is far from perfect, it's the first >step towards preventing major issues from being deployed on our users. > >If you are already using the mirror, you will need to either switch >branch manually, or re-add it. > > >2. The repository QA report [2] has been extended with some repository >statistics. In particular, the timestamp of the newest commit >and the number of valid (that is, those not dying in global scope) >ebuilds are reported. Additionally, the homepage link is now included >as well. > >This enables the Overlays team members to easily check which >repositories >are unmaintained and/or empty, and handle the issues more efficiently. >It can also be useful to users who want to figure out whether there's >a point in using a particular repository. > > >3. I've tried to optimize the logic used to run QA checks on >repositories, and I think I was able to even the load better. >Additionally, I've repacked the git repositories to get rid of huge >number of loose objects. > >As a result, CI now runs faster. The gentoo-ci runs are down from 10-12 >minutes to 7-8 minutes, and pull requests from 16-18 minutes to 9-14 >minutes. However, I don't have exact results yet as the server is still >busy removing old files ;-). > > >4. Finally, the mirroring code has been updated to correctly handle git >repositories for which 'master' is not the default branch. > > >Enjoy! > > >[1]:https://github.com/gentoo-mirror/gentoo >[2]:https://qa-reports.gentoo.org/output/repos/
Sounds like a big improvement. I'm not too familiar with CI, so forgive me if this is obvious: should overlays now use the 'stable' branch as their primary remote, so they can ensure that any breakage introduced is caused by their own overlay instead of a flub by us? If so, then I wonder if this will help indirectly improve overlay quality. Being able to say "as of X commit, the tree is in good shape" is a big deal imo. Thanks for working to make that happen. Is there anything other devs can do to assist your development, or do we stick to the usual 'if in doubt talk to QA'? - -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -----BEGIN PGP SIGNATURE----- iQJRBAEBCgA7NBxEYW5pZWwgQ2FtcGJlbGwgKEdlbnRvbyBEZXZlbG9wZXIpIDx6 bGdAZ2VudG9vLm9yZz4FAldUXhUACgkQASQOlFA54XC2HxAAx3HV3YbjfzEJg2FC 8QJus2qwU63+Agqr84R9X9zQMMUGqkRoFglNBg6slxdSzV3s/2SASYlj3ShGWLvR sYMgKXmDVvIZ/z5qaepIcmIz0pHc+NjITebZ+zq09IoH8uI2fFFNFibCNAwdz9X1 CWzj5q1i1D9LSaIU0Jmd9N21168V7jSViHx1HeRR/ECx8G0fvaC8mPxpiULmcdA2 ZWqzRfkXLeckNHfJsrQFQQR89WAa20IJSajTitkA9BejNZyMrnjALxFLx6reZ5W6 IK3KR2IaGgnjof5BfBoyX6q2MXT8psJZBusPeQvX1U8COfBFgpX1QfpDdEZzn1PF BQMOa2mqwHkk7dlL5VT5ue9towFCYpN/J0PJa8+bB+jmTXFgtHYPn50POEiyebyt il9+bieLs2jqGwIQBwhgwAwL6SXX0EcbyaW2Ja44A4z6e4kFAqgqifP2+C4g6l6Y Mz36uedDmviL1PWttAjsvROh4X6d1P3frWKdxnYYHdlYjFXig6pEZE87Hnxc3j0C wBGnYg5qUP8Q65MeLRzpPzBkxHJODgVEQP+sVM5f6Vs5RjAafApit/6SHgbzCqZH LB3MzYyReJOd/taCLfUgfBp0hnlOlSyuHT3sQmqjJpqPnwisoIEerWHJuUrp7Nn3 Fz19qALKqvESRV42YCz7Zy9Z+ig= =sgMj -----END PGP SIGNATURE-----
