Easily nerd sniped.
Tue, Apr 17
Github -> mirror to Diffusion -> deploy with puppet's ensure => latest is effectively deploying from Github, which we don't do. One of two things needs to happen as a gateway....
- We don't use ensure => latest in puppet, but rather a tag or sha1 to be explicit. This would require a puppet change on each update.
- We keep ensure => latest, but the mirroring to Diffusion isn't automatic.
In Design's case, we went with option (2) a few weeks ago. They push to Gerrit when they want to deploy, and puppet ensures the latest copy is pulled.
Either is fine by me, but (2) is probably less effort for your team for deploying.
Thu, Apr 12
No, that should've done it :(
Pretty sure that's unrelated....but I've definitely seen it before. Mostly when running maintenance scripts from tin instead of terbium. It kinda makes sense, considering tin wouldn't have the l10n cache locally (and I think mwscript tries to run it out of mediawiki-staging when on the deploy hosts).
That's a dupe of this....
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Time-out
Wed, Apr 11
Well ideally developers can use the same sets of charts, that's the main reason I thought of it as odd. docker-registry.wm.o seems nicer?
Do we really want this on integration.wm.o? Or is this only serving them from there for integration purposes? Just seems a little odd if this is the canonical location.
Tue, Apr 10
Approved by Releng.
Mon, Apr 9
A unicorn, I'll add, that was my suggestion ;-)
Professional? The cloud services logo is a unicorn.
I disagree with making it a config variable. We should support the env variable, yes, but otherwise we should expect the system we're on to do the right thing. Configuring this feels like it's just gonna bite us later.
Fri, Apr 6
Thu, Apr 5
My question too would be how well do these work out of the box? Is default config sufficient? Are there settings that must be configured? The installer lacks support in that area and I think it would confuse folks to click a checkbox and then nothing work.
Wed, Apr 4
(1) works for me too, actually.
18:43:56 py27: commands succeeded 18:43:56 py34: ignored failed command 18:43:56 SKIPPED: py35: InterpreterNotFound: python3.5 18:43:56 SKIPPED: py36: InterpreterNotFound: python3.6 18:43:56 flake8: commands succeeded 18:43:56 doc: commands succeeded 18:43:56 congratulations :)
- Add python3.4 too
I authorize this as @greg's delegate while he's on vacation.
Remember, Differential != Diffusion. There's a pretty obvious tail when it comes to Differential. I ran the numbers the other day and it was Scap, Blubber...then quickly drops off. Most repos have no differential revisions.
Tue, Apr 3
Option 3 is what I was learning towards in my initial work.
Yes. I'm not saying that code quality / dev interest are the reason we include them--they should be useful to the majority of our users. But because they're being bundled, they should be of good standards.
Mon, Apr 2
avatars-gravatar I am not installing. I did once, and was very quickly told not remove it. While that Wordpress proxy plugin solves the problem of performance/caching and exposing your IP to them, it still sends them your e-mail address. Just because e-mails are public doesn't mean we should broadcast them to a third party.
Been around a few releases back, fwiw.
I'm fine with moving Scap back to Gerrit tbh.
Thu, Mar 29
Wed, Mar 28
Tue, Mar 27
With AbuseFilter logging disabled in gerrit 421864 and CheckUser already disabled, I went ahead with truncating cu_changes and abuse_filter_log.
It wasn't meant to be a knowledge base of possibilities. You misunderstand the premise. The relation of T190676 to this was that it's an active issue people are currently having. The idea was to mention it to them on git operations.
I want to install this anyway to communicate downtime to users ahead of time.
Mon, Mar 26
I know nothing about langlinks.
Phabricator has the ability to unverify e-mails and thus disable outbound mail to it. In gerrit's case the ideal solution is being able to edit the user's preference to do so.
I can't speak for puppet, but the wmf-config repo doesn't have any other submodules slated for removal.
Yep, those are the ones.
This also isn't a Gerrit bug. Can easily replicate with Github or any other git server. Tbh, I'm not sure why this hasn't been an issue before...the workflow here hasn't changed: we prune these branches weekly and git gc I do from time to time.
Fri, Mar 23
Bump. Can we get this resolved for the remaining nodes?
Thu, Mar 22
Wed, Mar 21
This is still way more common than I'd like.
Mar 20 2018
Not using git-review will eliminate a few points of confusion I think :)
Mar 14 2018
Cf: scap update-interwiki-cache. It lets you do it all in one step :)
I can't think of any compelling reason why it would be *required* on the masters...but I could see it as being useful if you want to actually have your large file contents on the master if you're debugging/curious about something...?
Mar 13 2018
Mar 12 2018
Imported history from Github to Gerrit. Spoke with @Volker_E about the deployment process:
Yep, that's our SOP :)
If development is going to happen on Github I would call Gerrit a mirror yes. I don't see the problem
Done. Despite T115624 being closed there's plenty of other things the requestor can help with.