Still, unsurprisingly, a thing in 1.44.0-wmf.8 (T375667).

So I'm guessing this would work if just run as my user under _ssh_command_self, like it was before 3c40ccd2: fab: build images with user dockerpkg-builder.

Hmm, yeah. Doesn't seem like it was at any point either:

contint1002:/etc/docker-pkg/dev-images.yaml uses the same creds as integration.yaml, and that was at least working a few days ago.

Seems like it fits the rubric ok. I couldn't figure out how to change the privacy level of a repo in your namespace, so I instead made this one in the namespace we recently created for one-off projects that don't fit anywhere else:

Doesn't seem like there's an obvious way to just get a CLI push message, but it also doesn't really seem like we're losing a lot here. Let's call this one ok without it.

This is happening at a fairly low rate, so it seems like it doesn't warrant a rollback but should probably get a fix before we roll forward to group1.

Noting also that if it doesn't get a fix in time for @Aklapper's EU train window, I can pick things up during the US Wednesday workday.

Yeah, of stuff still defined in the repo, I think it's probably time to drop everything prior to Bookworm and everything prior to PHP 7.4, then build Bookworm defaults. Working up a couple of MRs for that.

Currently stable on all wikis.

@bvibber, @Umherirrender any thoughts on this one?

Noticed this just now while rolling 1.44.0-wmf.3 (T375662) to group0.

scap 4.123.0 has been deployed which should address this problem.

Note that this is asking for a project, and not a group as is typical at repos/<name>. We think this is appropriate for this use case as it is serving a cross-team and cross-functionality purpose, and on a technical level gitlab requires to publish to a project.

Sounds reasonable to me, i would go with wmf-packages to keep things slightly shorter

Now it's showing a message about signing up an account. As pushing code requires code, can we disable that too on pushes?

Might be worth investigating, but I'm guessing this is an upstream issue.

This is a banner that's set up for the web interface (for admins: this one).

For this reqId, also getting:

I'd say No, as you cannot reply to that very From address, and as it would very likely break things (people's mail filter rules etc) for little gain.

@brennen Can we chat about the "git status/git diff" in /srv/phab on phab1004 and the submodule situation? Maybe next office hours when we do another Phab deploy?

Also seeing this at:

We'll try to coordinate with you and do this early tomorrow, but feel free to do this yourself if we are not available.

@brennen Were you opped in #wikimedia-releng when you tried? You probably need to be opped to set this.

I get a You are not authorized to perform this operation. Have not really investigated deeply here...