JanZerebecki added a subscriber: JanZerebecki. JanZerebecki added a comment.
The fix to Wikidata to make it pass that job on master was done during https://phabricator.wikimedia.org/T117886. This problem was created because this job didn't run for Wikidata before, so when we enabled the job it was also enabled for old release branches, even though the fix to make the job pass was only merged in master. Builds for anything except master are done manually. You can update only one component by passing that as an argument like: `composer update data-values/value-view`. So there are a few options sorting by estimated work needed in increasing order: 1. Disable Wikidata and its tests on the release branches. 2. Make the Job skip Wikidata on release branches. Like https://gerrit.wikimedia.org/r/#/c/268790/ but it is more complicated, as the job mediawiki-extensions-qunit also contains a list of repos it pulls in when it is triggered from other repos. This can probably be done by duplicating this and the other gate jobs with one copy per release branch, each having a different set of extensions, but that is probably more clutter than is worth for old extensions without users (otherwise it would be worth it to fix the extension instead). 3. Backport fixes, which probably involves a new release of a few components branched from the version used in the release branch and at least one backport into the Wikibase release branch, then updating the Wikidata build from all that. 4. Setting the release branch to the current master version via a merge. (We probably broke compatibility with older core versions often enough, that this would involve quite some changes to make things backwards compatible.) To put this into perspective there are probably 0 users of Wikibase on release versions. I think I prefer solution 1, but find 3 acceptable (even though 3 is probably not worth the effort). It seems https://gerrit.wikimedia.org/r/#/c/268828/ is a combination of 1 and 3, I will comment there. In https://phabricator.wikimedia.org/T126073#2004067, @Paladox wrote: > @Mattflaschen ok. Is there any way we could prevent this happening to the > branches in the future. We probably would need to change how new jobs are enabled so that it doesn't affect old branches, which is not a small task. TASK DETAIL https://phabricator.wikimedia.org/T126073 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Paladox, JanZerebecki Cc: JanZerebecki, Krinkle, hashar, StudiesWorld, Paladox, Aklapper, gerritbot, Mattflaschen, Izno, Wikidata-bugs, matthiasmullie, aude, Gryllida, Mbch331, greg _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
