If we want to be able to provide Quickstart as a service to other developers, we need to run the commands in an CI environment. Every change we do, we want it to be tested so we are sure we do not break it.
Quickstart uses Docker containers, so our CI needs to be able to run Docker containers.
The CI also needs to support each operating system that we want to support. My guess is that we want the CI to run tests in:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Mhurd | T379222 Setup CI for quickstart | |||
| Resolved | Peter | T379220 POC: Try running mediawiki-quickstart on GitHub Actions | |||
| Resolved | • aborrero | T380335 Request creation of "mediawiki-quickstart" VPS project |
Ok VPS is in place with a single instance for now. Was able to get Docker working but I have a couple small permissions issues to resolve on such bare-metal Debian. I think I have a handle on the needed QuickStart tweaks, but will need to pick this back up tomorrow
I added more comments here:
https://wikimedia.slack.com/archives/C0337MKTPHD/p1731661897143049
Will comment here in this ticket from now on
Actually just got it working!
Will still need to make a couple tweaks though - back on it tomorrow
I'm most likely going to delete and re-create the instance tomorrow to ensure I have a handle on exactly what was actually needed to get everything set up - I have a WIP script that contains all the steps that I think were necessary.
Will use that fresh-start to further confirm any permissions related changes needed by QuickStart
This added a Quickstart project to Horizon:
https://phabricator.wikimedia.org/T380335
This added CI for Quickstart itself:
This encapsulates what was needed to provision VPS instances:
The changes mentioned above renamed your ci file to ci.components.selenium
Details:
https://gitlab.wikimedia.org/repos/qte/mediawiki-quickstart#ci
Next I'm looking at setting up a VPS instance for running your ci.components.selenium on a cron...
And one for running mediawiki core's selenium tests on a cron
Will probably name that ci file ci.core.selenium... or ci.mediawiki.selenium... hmm...
@Addshore Thanks for reminding me of this ticket! I forgot to close it after we set up the Gitlab runner and https://quickstart-ci-components.wmcloud.org