Change Details

As part of migrating m3api off of GitHub, all the current CI needs to be ported to GitLab. On GitHub, all the m3api libraries had two workflows, `test` and `release`. On GitLab, this corresponds to two stages with the same names. As of 2025-08-22, all the work related to this ticket is only on GitLab (not on GitHub), in repositories named “tmp-m3api*” (non-tmp repositories will be created only when everything is ready), on the `main` branch. Current status: - [m3api](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api): Contains a `.gitlab-ci-template.yml` file, with [hidden jobs](https://docs.gitlab.com/ci/jobs/#hide-a-job) used to template the CI in all libraries, and a `.gitlab-ci.yml` with the specific CI for the main m3api library (importing and extending the templates). - `test-job`, `test-package-lock-job` (imported from the template file), and `test-types-job` cover all the jobs in `.github/workflows/test.yaml`. - `release-job`, `publish-job`, and `doc-job` (all imported from the template file) cover all the jobs in `.github/workflows/release.yaml`. As mentioned in T392290#10782968, the order of operations is slightly different: there’s no support for triggering CI when a release is created; rather, `release-job` creates the release itself, while `publish-job` pushes it to npm (corresponds to GitHub’s `release` job). - TODO: `release-job` currently works around T333161 using a custom, non-WMCS image (the first option in T333161#10784529); clarify if this is okay and/or check if it still works with `tag: wmcs`. - There are variables on the `m3api` group with credentials for different environments: `MEDIAWIKI_PROD_BOT_USERNAME` + `MEDIAWIKI_PROD_BOT_PASSWORD` for Wikimedia production; `MEDIAWIKI_BETA_REAL_USERNAME` + `MEDIAWIKI_BETA_REAL_PASSWORD` for the beta cluster (actual user credentials, so m3api-oauth2 can log in in Selenium / WebdriverIO and approve an OAuth login); `MEDIAWIKI_BETA_BOT_USERNAME` + `MEDIAWIKI_BETA_BOT_PASSWORD` also for the beta cluster (bot password); and `MEDIAWIKI_BETA_OAUTH_CLIENT_ID` + `MEDIAWIKI_BETA_OAUTH_CLIENT_SECRET` + `MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_ID` + ``MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_SECRET` still for the beta cluster (OAuth client ID + secret, regular and non-confidential). The tests don’t use these directly; instead, they’re mapped into the environment variables the tests expect by the different CI files. (I might clean this up later, but it makes the migration easier to not rename the variables in the tests at first. In GitHub they’re just CI variables with the same names but for different environments on each repository, which is pretty confusing.) - Status: **complete**, I think, except for actually pushing docs to doc.w.o (blocked on {T392716}), and the TODOs mentioned above. - [m3api-botpassword](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-botpassword): Contains a `.gitlab-ci.yml` file importing and extending the templates. - `test-job` and `test-package-lock-job` cover all the jobs in `.github/workflows/test.yaml`. `test-job` is tagged `wmcs` as part of T397591; according to T397591#10939598 this was at some point not strictly necessary, but still seems generally nice. TODO: Check if this tag should perhaps be moved into the templates. (But note the potential conflict with `release-job` mentioned above.) - `release-job`, `publish-job` and `doc-job` cover all the jobs in `.github/workflows/release.yaml`, nothing special here. - Status: **complete** except for the TODO, I think. - [m3api-query](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-query): Contains a `.gitlab-ci.yml` file importing and extending the templates. - The same five jobs cover the same two workflows. Nothing special here whatsoever, I think. - Status: **complete**. - [m3api-oauth2](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-oauth2): Contains a `.gitlab-ci.yml` file importing and extending the templates, and a `.gitlab-ci-template.yml` file with another template for setting up a MediaWiki install against which to run the tests again. - The regular `test` job works, running browser tests against the beta cluster (using the `releng/node18-test-browser` image for this). The same caveat wrt the potential `wmcs` tag as for m3api-botpassword probably applies here as well. (At the moment, it seems to work fine from the default runners.) - The `test-slow` job uses a port of [setup-mediawiki](https://github.com/lucaswerkmeister/setup-mediawiki/) to run tests against a CI-local MediaWiki install with an artificially lowered `$wgOAuth2GrantExpirationInterval` (see T374562). TODO: Move this `.mediawiki-job` to another place, probably a dedicated repository like `repos/m3api/gitlab-templates` (where the “main” templates can also go, rather than living in `repos/m3api/(tmp-)m3api`). - Status: **complete**, just needs cleanup.

As part of migrating m3api off of GitHub, all the current CI needs to be ported to GitLab. On GitHub, all the m3api libraries had two workflows, `test` and `release`. On GitLab, this corresponds to two stages with the same names. As of 2025-08-24, most of the work related to this ticket is only on GitLab (not on GitHub), in repositories named “tmp-m3api*” (non-tmp repositories will be created only when everything is ready), on the `main` branch. Current status: - [ci-templates](https://gitlab.wikimedia.org/repos/m3api/ci-templates): Contains `test+release.yml` and `mediawiki.yml` files with [hidden jobs](https://docs.gitlab.com/ci/jobs/#hide-a-job) used to template the CI in all libraries. This is the only non-tmp repository so far. - `.test-job` and `.test-package-lock-job` cover the jobs in most repositories’ `.github/workflows/test.yaml`. - `.release-job`, `.publish-job`, and `.doc-job` cover all the jobs in the repositories’ `.github/workflows/release.yaml`. As mentioned in T392290#10782968, the order of operations is slightly different: there’s no support for triggering CI when a release is created; rather, `release-job` creates the release itself, while `publish-job` pushes it to npm (corresponds to GitHub’s `release` job). - TODO: `release-job` currently works around T333161 using a custom, non-WMCS image (the first option in T333161#10784529); clarify if this is okay and/or check if it still works with `tag: wmcs`. - Status: **Mostly complete** except for {T392716} and the TODO. - [m3api](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api): Contains a `.gitlab-ci.yml` importing and extending the templates. - In addition to `test-job` and `test-package-lock-job` (from the templates), there’s also a custom `test-types-job` to cover the rest of `.github/workflows/test.yaml`. - There are variables on the `m3api` group with credentials for different environments: `MEDIAWIKI_PROD_BOT_USERNAME` + `MEDIAWIKI_PROD_BOT_PASSWORD` for Wikimedia production; `MEDIAWIKI_BETA_REAL_USERNAME` + `MEDIAWIKI_BETA_REAL_PASSWORD` for the beta cluster (actual user credentials, so m3api-oauth2 can log in in Selenium / WebdriverIO and approve an OAuth login); `MEDIAWIKI_BETA_BOT_USERNAME` + `MEDIAWIKI_BETA_BOT_PASSWORD` also for the beta cluster (bot password); and `MEDIAWIKI_BETA_OAUTH_CLIENT_ID` + `MEDIAWIKI_BETA_OAUTH_CLIENT_SECRET` + `MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_ID` + ``MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_SECRET` still for the beta cluster (OAuth client ID + secret, regular and non-confidential). The tests don’t use these directly; instead, they’re mapped into the environment variables the tests expect by the different CI files. (I might clean this up later, but it makes the migration easier to not rename the variables in the tests at first. In GitHub they’re just CI variables with the same names but for different environments on each repository, which is pretty confusing.) - Status: **complete**. - [m3api-botpassword](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-botpassword): Contains a `.gitlab-ci.yml` file importing and extending the templates. - `test-job` and `test-package-lock-job` cover all the jobs in `.github/workflows/test.yaml`. `test-job` is tagged `wmcs` as part of T397591; according to T397591#10939598 this was at some point not strictly necessary, but still seems generally nice. TODO: Check if this tag should perhaps be moved into the templates. (But note the potential conflict with `release-job` mentioned above.) - `release-job`, `publish-job` and `doc-job` cover all the jobs in `.github/workflows/release.yaml`, nothing special here. - Status: **complete** except for the TODO, I think. - [m3api-query](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-query): Contains a `.gitlab-ci.yml` file importing and extending the templates. - The same five jobs cover the same two workflows. Nothing special here whatsoever, I think. - Status: **complete**. - [m3api-oauth2](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-oauth2): Contains a `.gitlab-ci.yml` file importing and extending the templates. - The regular `test` job works, running browser tests against the beta cluster (using the `releng/node18-test-browser` image for this). The same caveat wrt the potential `wmcs` tag as for m3api-botpassword probably applies here as well. (At the moment, it seems to work fine from the default runners.) - The `test-slow` job uses `mediawiki.yml` from the templates, a port of [setup-mediawiki](https://github.com/lucaswerkmeister/setup-mediawiki/), to run tests against a CI-local MediaWiki install with an artificially lowered `$wgOAuth2GrantExpirationInterval` (see T374562). - Status: **complete**.

As part of migrating m3api off of GitHub, all the current CI needs to be ported to GitLab. On GitHub, all the m3api libraries had two workflows, `test` and `release`. On GitLab, this corresponds to two stages with the same names. As of 2025-08-224, allmost of the work related to this ticket is only on GitLab (not on GitHub), in repositories named “tmp-m3api*” (non-tmp repositories will be created only when everything is ready), on the `main` branch. Current status: - [m3api- [ci-templates](https://gitlab.wikimedia.org/repos/m3api/tmp-m3apici-templates): Contains a `.gitlab-ci-template`test+release.yml` and `mediawiki.yml` file,s with [hidden jobs](https://docs.gitlab.com/ci/jobs/#hide-a-job) used to template the CI in all libraries,. and a `.gitlab-ci.yml` withThis is the specific CI for the main m3api library (importing and extending the templates)only non-tmp repository so far. - `- `.test-job`, ` and `.test-package-lock-job` (imported fromcover the template file), and `test-types-job` cover all the jobs in `jobs in most repositories’ `.github/workflows/test.yaml`. - `.release-job`, `.publish-job`, and `.doc-job` (all imported from the template file) cover all the jobs in the repositories’ `.github/workflows/release.yaml`. As mentioned in T392290#10782968, the order of operations is slightly different: there’s no support for triggering CI when a release is created; rather, `release-job` creates the release itself, while `publish-job` pushes it to npm (corresponds to GitHub’s `release` job). - TODO: `release-job` currently works around T333161 using a custom, non-WMCS image (the first option in T333161#10784529); clarify if this is okay and/or check if it still works with `tag: wmcs`. - Status: **Mostly complete** except for {T392716} and the TODO. - [m3api](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api): Contains a `.gitlab-ci.yml` importing and extending the templates. - In addition to `test-job` and `test-package-lock-job` (from the templates), there’s also a custom `test-types-job` to cover the rest of `.github/workflows/test.yaml`. - There are variables on the `m3api` group with credentials for different environments: `MEDIAWIKI_PROD_BOT_USERNAME` + `MEDIAWIKI_PROD_BOT_PASSWORD` for Wikimedia production; `MEDIAWIKI_BETA_REAL_USERNAME` + `MEDIAWIKI_BETA_REAL_PASSWORD` for the beta cluster (actual user credentials, so m3api-oauth2 can log in in Selenium / WebdriverIO and approve an OAuth login); `MEDIAWIKI_BETA_BOT_USERNAME` + `MEDIAWIKI_BETA_BOT_PASSWORD` also for the beta cluster (bot password); and `MEDIAWIKI_BETA_OAUTH_CLIENT_ID` + `MEDIAWIKI_BETA_OAUTH_CLIENT_SECRET` + `MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_ID` + ``MEDIAWIKI_BETA_OAUTH_NONCONFIDENTIAL_CLIENT_SECRET` still for the beta cluster (OAuth client ID + secret, regular and non-confidential). The tests don’t use these directly; instead, they’re mapped into the environment variables the tests expect by the different CI files. (I might clean this up later, but it makes the migration easier to not rename the variables in the tests at first. In GitHub they’re just CI variables with the same names but for different environments on each repository, which is pretty confusing.) - Status: **complete**, I think, except for actually pushing docs to doc.w.o (blocked on {T392716}), and the TODOs mentioned above. - [m3api-botpassword](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-botpassword): Contains a `.gitlab-ci.yml` file importing and extending the templates. - `test-job` and `test-package-lock-job` cover all the jobs in `.github/workflows/test.yaml`. `test-job` is tagged `wmcs` as part of T397591; according to T397591#10939598 this was at some point not strictly necessary, but still seems generally nice. TODO: Check if this tag should perhaps be moved into the templates. (But note the potential conflict with `release-job` mentioned above.) - `release-job`, `publish-job` and `doc-job` cover all the jobs in `.github/workflows/release.yaml`, nothing special here. - Status: **complete** except for the TODO, I think. - [m3api-query](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-query): Contains a `.gitlab-ci.yml` file importing and extending the templates. - The same five jobs cover the same two workflows. Nothing special here whatsoever, I think. - Status: **complete**. - [m3api-oauth2](https://gitlab.wikimedia.org/repos/m3api/tmp-m3api-oauth2): Contains a `.gitlab-ci.yml` file importing and extending the templates, and a `.gitlab-ci-template.yml` file with another template for setting up a MediaWiki install against which to run the tests again. - The regular `test` job works, running browser tests against the beta cluster (using the `releng/node18-test-browser` image for this). The same caveat wrt the potential `wmcs` tag as for m3api-botpassword probably applies here as well. (At the moment, it seems to work fine from the default runners.) - The `test-slow` job uses a port of [setup-mediawiki](https://github.com/lucaswerkmeister/setup-mediawiki/) to run tests against a CI-local MediaWiki install with an artificially lowered `$wgOAuth2GrantExpirationInterval` (see T374562).`mediawiki.yml` from the templates, TODO: Move this `.mediawiki-job` to another place, probably a dedicated repository like `repos/m3api/gitlab-templates` (where the “main” templates can also goa port of [setup-mediawiki](https://github.com/lucaswerkmeister/setup-mediawiki/), rather than living in `repos/m3api/(tmp-)m3api`to run tests against a CI-local MediaWiki install with an artificially lowered `$wgOAuth2GrantExpirationInterval` (see T374562). - Status: **complete**, just needs cleanup.