Page MenuHomePhabricator

Extend functionality to support MediaWiki infrastructure Windows and related repos
Open, In Progress, MediumPublicFeature

Description

What?

We would like to request to extend the schedule-deployment tool to support:

  • MediaWiki infrastructure Windows
    • operations/deployment-charts repo
  • Puppet Request Windows
    • operations/puppet repo

Why?
SREs have three MediaWiki infrastructure deployment windows per day. Typically, these windows are utilised without posting the forthcoming changes in the Deployment Calendar, unless they are particularly significant (eg DC switchover).

I believe that simplifying the process of recording such changes to the Deployment Calendar, will enable SREs to post on the Dev Calendar more regularly, improving visibility (and communication in a way)

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Support MediaWiki infrastructure schedulingtoolforge-repos/schedule-deployment!23jijimediawiki-infra-windowsmain
Customize query in GitLab

Event Timeline

jijiki updated the task description. (Show Details)
bd808 changed the subtype of this task from "Task" to "Feature Request".Jan 29 2025, 4:50 PM

I came across this task in the process of scheduling https://gerrit.wikimedia.org/r/c/operations/puppet/+/1238369 for a puppet request window (and seeing if Tool-schedule-deployment would be able to do it for me).
It seems like this feature might be nice to have, at least for puppet requests (I can't personally speak to infra windows) :)

This would be a lot less painful to implement if something like T366880: Consider using JSON content model for deployment calendar were done first. The business logic used by Tool-schedule-deployment to parse wikitext into structured data is horrible. Like seriously horrible. I committed these crimes against python because way too many people were spending way too much time editing the Deployments page for backports. I totally agree that it would be nice to generalize things so that other types of assisted deployments were easier to manage too. I just don't want to be on the hook for fixing the myriad ways that can be broken compounding the existing problems of the current use case.

Fair, fair :) (To be clear, my comment should just be taken as a general +1 towards the idea, rather than trying to obligate anyone to work on it right now, esp. given what you've said!)

RLazarus changed the task status from Open to In Progress.May 6 2026, 8:14 PM
RLazarus assigned this task to jijiki.
RLazarus moved this task from Inbox to In Progress on the ServiceOps new board.
RLazarus subscribed.

Posting as serviceops triage: Adding Releng for awareness (who don't own the schedule-deployment tool but do manage other deployment calendar automation).

Posting as a Puppet window deployer: I have a draft in progress that will eliminate the mostly-unused Puppet window in favor of an async process, which I expect to be better for both requesters and SREs. That hasn't happened yet, as it's been delayed by other work, but I don't recommend investing engineering time in the Puppet window. For the MW infra window though, sounds good to me.

RLazarus triaged this task as Medium priority.May 6 2026, 8:14 PM