Hello,
Sorry to resurrect this old thread but I came across some issues while attempting to upload the initial configuration for a new chapter wiki[1].
The new composer commands do look for an entry in wikiversions.json no matter what, apparently; and refuse to work if they find none. I am not sure if we want that behaviour, considering that it takes weeks after the initial configuration gets uploaded for a wiki to be created, and wikiversions.json changes thrice per week due to the mediawiki trains.
I used to upload configuration patches without that entry on purpose so it was easier to rebase once the configuration patch was about to be merged. I did the trick locally adding a wikiversion.json entry, running the composer commands but not committing the wikiversions file later; however that also causes Jenkins to fail as it detects wikis in all.dblists in all but not in wikiversions.json.
`composer test` also failed due to some weird errors[2] which I'm not sure are relevant for local testing: TimelineTest::testTimelineFontFileEexists.
Also, on the Wikitech guide[3] there's no mention of this new procedure. We should be updating it I guess.
Best regards, M.
[1]: https://gerrit.wikimedia.org/r/574184/ [2]: https://phabricator.wikimedia.org/P10477 [3]: https://wikitech.wikimedia.org/wiki/Add_a_wiki#MediaWiki_configuration
El lun., 2 dic. 2019 a las 17:19, James Forrester (jforrester@wikimedia.org) escribió:
On Wed, 27 Nov 2019 at 23:44, Martin Urbanec martin.urbanec@wikimedia.cz wrote:
Hello,
to ensure my understanding is correct, is the correct way to do dblists changes nowadays to first change yaml and then run composer build?
Yes.
J.
James D. Forrester (he/him or they/themself) Wikimedia Foundation
-- To unsubscribe from this group and stop receiving emails from it, send an email to sitereq-l+unsubscribe@wikimedia.org.