User Details
- User Since
- Feb 7 2022, 1:09 PM (145 w, 6 d)
- Roles
- Administrator
- Availability
- Available
- LDAP User
- Jaime Nuche
- MediaWiki User
- JNuche (WMF) [ Global Accounts ]
Fri, Nov 22
Discussed with @EBomani it's fine to just remove the cronjob for now. No need to clean the redirection dirs
Thu, Nov 21
Wed, Nov 20
Tue, Nov 19
Mon, Nov 18
Fri, Nov 15
Thu, Nov 14
Wed, Nov 13
Tue, Nov 12
Script works outside of the container apparently:
Mon, Nov 11
Ooops, I totally missed that AC from the description, really sorry about that. I only verified that the environment started up correctly and that I could see the relevant extensions on Special:Version.
k3s-data volume usage breakdown
Fri, Nov 8
Deployed to prod
Trying to bring this to the attention of someone who is able to help. There is a related pending patch in T379217
Thu, Nov 7
Release Jenkins instances upgraded in prod. I verified LDAP login still works.
Deployed to prod
Wed, Nov 6
The is already fixed in T378261 (1.44.0-wmf.2). The fix was not backported to 1.44.0-wmf.1. Only error level downgrading was.
Confirmed that RC entries are now displayed correctly as bot changes after backporting the fix: https://www.mediawiki.org/wiki/Special:RecentChanges?hidebots=0
Marking as UN! as per T375661#10293865
Tue, Nov 5
Can confirm the error is gone from the logs. Thanks @Lucas_Werkmeister_WMDE and @Reedy !
Upstream is also updating the plugins parent pom to a version that requires this 2.479.1 and I have some patches for plugins that would end up requiring it in order to be updated on our instance :)
Thanks @Tgr
Was this motivated by https://issues.jenkins.io/browse/JENKINS-73760?
Train now got past the failing stage. Removing this as a blocker
More details, successful backports were still happening yesterday, e.g.: https://sal.toolforge.org/log/6iIf-ZIBFFSCpsJz1WyO
I assume the active deployment server?