I did my first fully self-run config deploy with SpiderPig the other day
and it was _smooth sailing_. Very nice! Much cleaner than futzing about
with the command-line, and I feel more confident now being able to push my
own high-prio fixes outside a backport window  without it stepping on other
peoples' toes. \o/

Much thanks to all involved!

-- brooke

On Thu, May 8, 2025 at 7:01 AM Tyler Cipriani <tcipri...@wikimedia.org>
wrote:

> tl;dr: Check out SpiderPig[0], a web frontend for deploying code
> changes to Wikimedia’s MediaWiki.
>
> —
>
> What is SpiderPig?
>
> SpiderPig is a web app that deploys code to Wikimedia’s production
> MediaWikis.
>
> —
>
> How do I use it?
>
> Today, anyone who has deployed a backport in the past year[1] can log
> in at https://spiderpig.wikimedia.org.
>
> Follow instructions on Wikitech to learn how to use SpiderPig[2] or
> request access[3].
>
> Join Release Engineering for a deployment party 🥳 to try out SpiderPig:
>
> *Mon, 12 May 2025* – *Thu, 15 May 2025* members of Release Engineering
> will be in the #wikimedia-operations IRC channel for daily backport
> windows to share the joy of SpiderPig:
>
> - UTC afternoon backport window (13:00 UTC)
> - UTC late backport window (20:00 UTC)
>
> More details on the deployment calendar.[4]
>
> —
>
> Why?
>
> During backport windows[5], deployers traditionally use our `scap
> backport` command-line tool to ship code. Meanwhile, developers wait
> on standby to check the code.
>
> For many deployments, deployers punch in commands and relay
> information to developers. SpiderPig eliminates the need to punch in
> commands for simple changes, freeing deployers to focus on complex
> changes.
>
> SpiderPig is like showing up for a backport window to get a change
> deployed:
>
> Enter a Gerrit change number in the search and click “Start backport.”
> When prompted, check it on the staging servers[6].
> Confirm that the change looks good on staging to make it live everywhere!
>
> —
>
> Thanks to:
>
> - Alexandros Kosiaris for his partnership in getting SpiderPig into
> production.
> - Lauralyn Watson, Eric Gardner, and other folks working on Codex for
> their help integrating Codex and Vue.
> - Simon Lyngshede and Moritz Mühlenhoff for their help integrating
> with our single sign-on system.
> - Ahmon Dancy for leading this project and the Release Engineering
> team for all their work to make deployments better.
>
> Tyler Cipriani (he/him)
> Engineering Manager, Release Engineering
> Wikimedia Foundation
>
> [0]: <https://wikitech.wikimedia.org/wiki/Scap/SpiderPig>
> [1]: <https://ldap.toolforge.org/group/spiderpig-access>
> [2]: <
> https://wikitech.wikimedia.org/wiki/Scap/SpiderPig#Log_in_to_SpiderPig>
> [3]: <
> https://wikitech.wikimedia.org/wiki/Scap/SpiderPig#Access_to_SpiderPig>
> [4]: <https://wikitech.wikimedia.org/wiki/Deployments>
> [5]: <https://wikitech.wikimedia.org/wiki/Backport_windows>
> [6]: <https://wikitech.wikimedia.org/wiki/WikimediaDebug>
> _______________________________________________
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
_______________________________________________
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

Reply via email to