[Wikitech-l] Re: Sponsored-by

On Thu, May 27, 2021 at 08:04:23PM +0200, David Caro wrote: > I'm willing to help with some scripts/hooks to set it up if needed > (though I'm suspicious they already exist xd). I added a line to my git commit template, and it suffices for me so far. I'm sure this can be made smoother. -- WMF

[Wikitech-l] Sponsored-by

I figure this might be of interest to some here: we could make sponsorship of contributions more evident by adding a git commit pseudo-header: Sponsored-by: Name Of Sponsoring Entity Obviously this would be optional, and only used by those who want to. Spelled out in a little more detail:

[Wikitech-l] The deployment of 1.37.0-wmf.3: rocky, but good now

This is a summary of this week's deployment of the 1.37.0-wmf.3 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week was me, Lars Wirzenius, with Jeena Huneidi as backup, both from the Release Engineering team. The summary task for

[Wikitech-l] [Train] 1.37.0-wmf.3 status update

The 1.37.0-wmf.3 version of MediaWiki is blocked[0]. The new version is deployed to {group(s){0,1,2}}[1], but can proceed no further until these issues are resolved: * T281361 TypeError: Argument 2 passed to

[Wikitech-l] Summary of this week's deployment of 1.37.0-wmf.1: all good!

This is a summary of this week's deployment of the 1.37.0-wmf.1 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week is Jeena Huneidi, with Dan Duvall as backup, both from the Release Engineering team. The summary task for this week is

[Wikitech-l] Summary of this week's deployment of 1.36.0-wmf.38: not there yet

(This is almost a repeat of last week's train summary. It's again a short week and the train is still running.) This is a summary of this week's deployment of the 1.36.0-wmf.38 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week is Dan

[Wikitech-l] Summary of this week's deployment of 1.36.0-wmf.36: not there yet

This is an early summary of this week's deployment of the 1.36.0-wmf.37 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week is Mukunda Modell, with Antoine Musso as backup, both from the Release Engineering team. The summary task for this

[Wikitech-l] Summary of this week's deployment of 1.36.0-wmf.36

This is a summary of this week's deployment of the 1.36.0-wmf.36 branch of MediaWiki and its extensions. The primary person in charge this week is Antoine Musso, with Ahmon Dancy as backup, both from the Release Engineering team. The summary task for this week is

[Wikitech-l] Summary of this week's deploymentt of 1.36.0-wmf.35

This is a summary of this week's deployment of the 1.36.0-wmf.35 branch of MediaWiki and its extensions. The primary person doing this was Ahmon Dancy, with Brennen Bearnes as backup, both from the Release Engineering team. Overall this week was not entirely smooth, but not too bad. The branch

Re: [Wikitech-l] Train status: on all wikis, looking good

Train has reached all wikis about 1.5 hours ago, and things look OK. Unless something bad happens soon, this week's train deployment is over and I shan't say more. If something does come up, there will be further communications. If all goes well, have a good Friday and weekend. Be well. Be safe.

[Wikitech-l] Train status: at group1 and OK

The train blocker[0] mentioned earlier was worked around and train was unblocked. It's now at group1. Watching logs to see if there's any further breakage. Thank you to Majavah, Urbanecem, and Vlad.shapik (who came up the patch) for unblocking train. Train will move forward tomorrow to group2,

[Wikitech-l] [Train] 1.36.0-wmf.33 status update: blocked at group0

The 1.36.0-wmf.33 version of MediaWiki is blocked[0]. The new version is deployed to group0[1], but can proceed no further until these issues are resolved: * T276316 - Argument 1 passed to getCanonical() must be of the type string, null given, called in CentralAuthGroupMembershipProxy.php -

[Wikitech-l] Train status: at group0 and OK

A short status update about this week's train, 1.36.0-wmf.33. I've deployed MediaWiki version 1.36.0-wmf.33 to group0. Everything seems to be OK after an hour. There are currently no blockers. Thank you everyone involved in MediaWiki development and running Wikimedia servers for the lack of bumps

[Wikitech-l] [Train] 1.36.0-wmf.9 status update

The 1.36.0-wmf.9 version of MediaWiki is blocked[0]. The previous train blocker was resolved, and train moved to group1. The new version is deployed to groups{0,1}[1], but can proceed no further until these issues are resolved: * T263034 PHP Notice: Trying to get property 'textContent' of

[Wikitech-l] [Train] 1.36.0-wmf.0 status update

The 1.36.0-wmf.9 version of MediaWiki is blocked[0]. The new version is deployed to nowhere at all, including not even on testwikis, but can proceed no further until these issues are resolved: * T262900 Rebuilding l10n cache fails for train - https://phabricator.wikimedia.org/T262900 Once this

[Wikitech-l] scap sync now called scap sync-world

Hi, I tagged a new release of Scap (3.15.0) yesterday, which will hopefully be installed on the various servers next week. One of the changes is that "scap sync" now gives and error, and directs the user to use "scap sync-world" or "scap sync-file", depending on what they meant to do. This

[Wikitech-l] scap sync --canary-wait-time option (new)

The 3.14.0 release of Scap (current version) added the --canary-wait-time option to the sync subcommand (which the next version of Scap will rename to sync-world). This sets the time how long Scap waits for code to run on canary servers. The default is 20 seconds, but if that is too long or too

[Wikitech-l] [Train] 1.35.0-wmf.37 status update

The 1.35.0-wmf.37 version of MediaWiki is blocked[0]. The new version is deployed to group0[1], but can proceed no further until these issues are resolved: * Watchlist star gone on Vector - https://phabricator.wikimedia.org/T255574 Once these issues are resolved train can resume. Normally,

[Wikitech-l] "scap sync" getting renamed to "scap sync-world"

The next release of Scap, our deployment tool, renames the "scap sync" subcommand to "scap sync-world". The sync command should mostly only be used by Release Engineering during train deployments, and SWAT folks updating l10n; everyone else almost certainly wants "scap sync-file" instead. The

Re: [Wikitech-l] [Ops] [Train] 1.35.0-wmf.3 status update

The blockers were quickly dealt with, thanks! We're at 1.35.0-wmf.3 on all wikis now. On Thu, Oct 24, 2019 at 03:30:54PM +0300, Lars Wirzenius wrote: > The 1.35.0-wmf.3 version of MediaWiki is blocked[0]. > > The new version is deployed to groups 0 and 1[1], but can proceed no > f

Re: [Wikitech-l] [Ops] [Train] 1.35.0-wmf.3 status update

The 1.35.0-wmf.3 version of MediaWiki is blocked[0]. The new version is deployed to groups 0 and 1[1], but can proceed no further until these issues are resolved: * Call to undefined method Wikibase\Lib\EntityTypeDefinitions::getPrefetchingTermLookupCallbacks()

[Wikitech-l] [Train] 1.35.0-wmf.3 status update]

(Re-send to wikitech-l, first attampt had wrong address.) The 1.35.0-wmf.3 version of MediaWiki is blocked[0]. The new version is not deployed anywhere[1], and can proceed no further until these issues are resolved: * scap sync failed, database error - https://phabricator.wikimedia.org/T236166

[Wikitech-l] 1.34.0-wmf.14 status update

The 1.34.0-wmf.14 version of MediaWiki is blocked[0]. The new version is deployed to {group0}[1], but can proceed no further until these issues are resolved: * TopicListBlock.php sort order params - * RevisionFormatter.php: Unknown content format -

[Wikitech-l] Future CI planning, feedback requested

In the Release Engineering team we're preparing for a new CI system. The current one needs to be replaced. It works well, but parts of it are getting obsolete. In particular, the Zuul version we use is obsoleted by upstream. The new version of Zuul is entirely different. Because of this, we are

Re: [Wikitech-l] CI jobs run time

On Sun, Jun 16, 2019 at 08:07:02PM +0200, Amir Sarabadani wrote: > In the past couple of weeks, jenkins jobs became considerably slow. There > has been some actions to improve it. Excellent! I'm very glad to hear about these improvements. Software development is a set of concentric loops, the

Re: [Wikitech-l] Gerrit outage

On Wed, Mar 20, 2019 at 06:56:19PM +, Pine W wrote: > I'd like to give a quick thanks to folks who have been dealing with > turbulence. Me too. It's inspirational and awe-inspiring to see people work on this. ___ Wikitech-l mailing list

[Wikitech-l] Choosing tools for continuous integration

The Release Engineering team has started a working group to discuss and consider our future continuous integration tooling. Please help! The RelEng team is working with SRE to build a continuous delivery and deployment pipeline, as well as changing production to run things in containers under

Re: [Wikitech-l] Collecting UI feedback for PolyGerrit - Gerrit

I've implemented some like that for my personal issue tracker, based on the PGP word list (https://en.wikipedia.org/wiki/PGP_word_list). Each ticket id is converted into hexadecimal, and the first six hex digit are used to look up word. For example, I have tickets such as "REPAY RETRACTION MERIT"