[05:40:38] <wmf-insecte>	 Project beta-update-databases-eqiad build #70582: 04FAILURE in 20 min: https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/70582/
[07:05:01] <wmf-insecte>	 Project beta-update-databases-eqiad build #70583: 15ABORTED in 45 min: https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/70583/
[07:46:03] <dwalden>	 I think beta is down. I just get "Unable to connect".
[07:48:27] <dwalden>	 Might be https://phabricator.wikimedia.org/T347665
[07:52:10] <RhinosF1>	 dwalden: a lot of cloud vps is badly broken
[07:52:14] <RhinosF1>	 So I'd guess probably
[08:05:01] <wmf-insecte>	 Project beta-update-databases-eqiad build #70584: 15ABORTED in 45 min: https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/70584/
[08:12:24] <wmf-insecte>	 Project mediawiki-core-doxygen-docker build #46750: 04FAILURE in 8 min 17 sec: https://integration.wikimedia.org/ci/job/mediawiki-core-doxygen-docker/46750/
[08:20:04] <wmf-insecte>	 Project beta-update-databases-eqiad build #70585: 04STILL FAILING in 3.7 sec: https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/70585/
[09:17:30] <wmf-insecte>	 Yippee, build fixed!
[09:17:30] <wmf-insecte>	 Project mediawiki-core-doxygen-docker build #46751: 09FIXED in 8 min 35 sec: https://integration.wikimedia.org/ci/job/mediawiki-core-doxygen-docker/46751/
[09:30:17] <wmf-insecte>	 Yippee, build fixed!
[09:30:17] <wmf-insecte>	 Project beta-update-databases-eqiad build #70586: 09FIXED in 10 min: https://integration.wikimedia.org/ci/job/beta-update-databases-eqiad/70586/
[11:08:03] <jelto>	 Gitlab needs a short downtime at roughly 13:00 UTC
[11:12:12] <jelto>	 update: downtime will be a bit earlier, roughly 12:30 UTC
[11:55:00] <hashar>	 !log Reloading Zuul for https://gerrit.wikimedia.org/r/c/integration/config/+/961778 "add edit-analytics and page-analytics"
[11:55:02] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL
[11:58:47] <hashar>	 !log Reloading Zuul for https://gerrit.wikimedia.org/r/c/integration/config/+/961778 "add edit-analytics and page-analytics" T336391 T336385 T336415
[11:58:53] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL
[11:58:53] <stashbot>	 T336415: Editor analytics service: Configure routing in staging and production - https://phabricator.wikimedia.org/T336415
[11:58:54] <stashbot>	 T336391: AQS 2.0: Page Analytics Service: Deploy to staging and production - https://phabricator.wikimedia.org/T336391
[11:58:54] <stashbot>	 T336385: Edit Analytics: Deploy to staging and production - https://phabricator.wikimedia.org/T336385
[12:47:29] <wikibugs>	 10GitLab (Integrations), 10Phabricator, 10Release-Engineering-Team (Escape Goats🐐), 10collaboration-services: Get GitLab to render `T{\d}+` in MR overviews, comments, etc. as links to Phabricator - https://phabricator.wikimedia.org/T337570 (10Jelto) Usage of a local gemfile causes problems when doing a Git...
[12:47:37] <wikibugs>	 10GitLab (Integrations), 10Phabricator, 10Release-Engineering-Team (Escape Goats🐐), 10collaboration-services: Get GitLab to render `T{\d}+` in MR overviews, comments, etc. as links to Phabricator - https://phabricator.wikimedia.org/T337570 (10Jelto)
[14:16:15] <wmf-insecte>	 Project beta-scap-sync-world build #122782: 04FAILURE in 1 min 7 sec: https://integration.wikimedia.org/ci/job/beta-scap-sync-world/122782/
[14:26:18] <wmf-insecte>	 Yippee, build fixed!
[14:26:19] <wmf-insecte>	 Project beta-scap-sync-world build #122783: 09FIXED in 1 min 11 sec: https://integration.wikimedia.org/ci/job/beta-scap-sync-world/122783/
[14:56:19] <wmf-insecte>	 Project beta-scap-sync-world build #122786: 04FAILURE in 1 min 11 sec: https://integration.wikimedia.org/ci/job/beta-scap-sync-world/122786/
[14:56:26] <brett>	 Hello. I apologize in advance for this....
[14:56:30] <brett>	 Traffic is beginning the migration from gerrit to gitlab. As we'll handle our own CI I have a few questions about "best practices" for WMF.
[14:56:32] <brett>	 Do we own our own traffic container images for testing? If so, it'd be good to figure out how we should go about that: For instance, our first project, acme-chief, needs Python as well as Go to run tests. So already we likely need our own custom image.
[14:56:34] <brett>	 Would we then create an image specifically for acme-chief testing? A base traffic image that other images build upon for specific project tests? One singular monster Debian image with everything just shoved in there? Is there an expectation of using a specific base? Avoiding upstream registries in favor of our own?
[15:06:20] <wmf-insecte>	 Yippee, build fixed!
[15:06:20] <wmf-insecte>	 Project beta-scap-sync-world build #122787: 09FIXED in 1 min 10 sec: https://integration.wikimedia.org/ci/job/beta-scap-sync-world/122787/
[15:15:50] <dancy>	 brett:  https://gitlab.wikimedia.org/repos/releng/kokkuri#using-published-images-in-downstream-jobs describes how you can use gitlab CI to create a custom image that is used by subsequent jobs.  You can use any base image that you want, unless you intend to publish an image to the docker-registry.wikimedia.org, in which case the base image needs to come from docker-registry.wikimedia.org as well.
[15:22:09] <brett>	 dancy: Thank you! I'll peruse this and absorb the knowledge
[15:33:03] <wikibugs>	 10GitLab (CI & Job Runners), 10collaboration-services, 10serviceops: Standardize Debian package builds on GitLab CI - https://phabricator.wikimedia.org/T304491 (10MatthewVernon) ...now with added build tagging too :)
[15:40:49] <wikibugs>	 10Project-Admins: Requests for addition to the #acl*Project-Admins group (in comments) - https://phabricator.wikimedia.org/T706 (10KStoller-WMF) Hello! I would like to request access to additional permissions because I'm the Product Manager of the #growth-team, and we are experimenting with moving towards a more...
[16:25:04] <wikibugs>	 10Project-Admins: Requests for addition to the #acl*Project-Admins group (in comments) - https://phabricator.wikimedia.org/T706 (10Ladsgroup) >>! In T706#9211237, @KStoller-WMF wrote: > Hello! I would like to request access to additional permissions because I'm the Product Manager of the #growth-team, and we are...
[16:31:31] <wikibugs>	 (03PS1) 10C. Scott Ananian: Zuul: [mediawiki/libs/JsonCodec] Add basic tests [integration/config] - 10https://gerrit.wikimedia.org/r/962063
[16:33:15] <wikibugs>	 (03CR) 10Reedy: [C: 03+2] Zuul: [mediawiki/libs/JsonCodec] Add basic tests [integration/config] - 10https://gerrit.wikimedia.org/r/962063 (owner: 10C. Scott Ananian)
[16:34:29] <wikibugs>	 (03Merged) 10jenkins-bot: Zuul: [mediawiki/libs/JsonCodec] Add basic tests [integration/config] - 10https://gerrit.wikimedia.org/r/962063 (owner: 10C. Scott Ananian)
[16:35:17] <Reedy>	 !log Reloading Zuul to deploy https://gerrit.wikimedia.org/r/962063
[16:35:20] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL
[16:36:25] <wikibugs>	 (03CR) 10C. Scott Ananian: "This change is ready for review." [libs/JsonCodec] (refs/meta/config) - 10https://gerrit.wikimedia.org/r/962017 (owner: 10C. Scott Ananian)
[16:36:34] <wikibugs>	 (03CR) 10C. Scott Ananian: [V: 03+2 C: 03+2] Edit Repo Config [libs/JsonCodec] (refs/meta/config) - 10https://gerrit.wikimedia.org/r/962017 (owner: 10C. Scott Ananian)
[17:11:39] <wikibugs>	 10GitLab (Project Migration), 10SRE, 10Traffic: Migrate Traffic repositories from Gerrit to Gitlab - https://phabricator.wikimedia.org/T347623 (10LSobanski) As long as the parent ticket is more or less up to date, that works for me, thanks for asking.  As for archiving the repositories on Gerrit, this requir...
[18:37:29] <wikibugs>	 10Release-Engineering-Team (Priority Backlog 📥), 10collaboration-services: Migrate SRE repositories to GitLab - Archiving unused Gerrit repositories - https://phabricator.wikimedia.org/T343707 (10thcipriani)
[19:13:52] <wikibugs>	 10Project-Admins: Create milestone tag for Ultraviolet/RedWarn Compatibility - https://phabricator.wikimedia.org/T347760 (10Sportzpikachu)
[21:42:40] <brett>	 I've been learning more about blubber, which appears to be the tool recommended for creating the container image we need for CI. I'm unable to locate any analog to a Dockerfile's RUN directive. Is that absent? The image would need to run a few commands to prepare the environment that is not provided by the pre-defined builders
[21:43:07] <wikibugs>	 10Release-Engineering-Team (Priority Backlog 📥), 10collaboration-services: Migrate SRE repositories to GitLab - Archiving unused Gerrit repositories - https://phabricator.wikimedia.org/T343707 (10thcipriani) >>! In T343707#9182549, @LSobanski wrote: > operations/software/schema-changes  This one seems to have...
[21:46:14] <brett>	 The kokkuri link that was shared earlier mentions using .kokkuri:build-and-publish-image but I'm not really seeing how one can run commands to extend the image
[21:47:31] <brett>	 I was thinking that by creating a .pipeline/blubber.yaml file I could create the necessary container image with python+go and modules. But that's not even the same project that was linked earlier so I feel like I'm off-base now ^^;
[22:19:14] <wikibugs>	 10Release-Engineering-Team (Priority Backlog 📥), 10collaboration-services: Migrate SRE repositories to GitLab - Archiving unused Gerrit repositories - https://phabricator.wikimedia.org/T343707 (10Peachey88)
[23:09:59] <wikibugs>	 10GitLab (Misc), 10Release-Engineering-Team (Escape Goats🐐), 10User-aborrero: Investigate and document stacked merge requests - https://phabricator.wikimedia.org/T300819 (10thcipriani) >>! In T300819#9046388, @cscott wrote: > This seems related to the general 'Depends-On' feature in gerrit/jenkins, which I t...