In T224979: Parsoid REST Routes Extension, we have turned the Parsoid library repo into a makeshift extension, to use for testing core integration until the codebase stabilizes and can be moved into core (or maybe a proper extension). We'll need to set up extension tests for that.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T225730 Reduce runtime of MW shared gate Jenkins jobs to 5 min | |||
Open | None | T226869 Run browser tests in parallel | |||
Resolved | None | T285649 Switch all Quibble Selenium and api-testing jobs to use apache | |||
Open | None | T261329 Prepare Parsoid for MW | |||
Resolved | Arlolra | T248694 Improve testing of Parsoid/PHP (1.36) | |||
Open | None | T227352 Set up extension tests for Parsoid repo | |||
Resolved | cscott | T248726 Run phan on code in extension/ |
Event Timeline
Should be straight forward. It is usually all about adding an entry in integration/config.git in zuul/layout.yaml
We should update our developer docs as well to reflect best practices to installing Parsoid & running PHP tests. Should Parsoid be installed inside core/extensions/Parsoid and/or is setting $MW_INSTALL_PATH sufficient? Ideally composer extension-test or something would Do The Right Thing assuming proper set up (whether that's installing Parsoid inside the extension folder or setting MW_INSTALL_PATH or whatever else the Right Thing needs to be).
Since Parsoid/PHP is in production, a train rollout without proper integration testing could have dire effects.
Change 612430 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
[integration/config@master] Turn on standard quibble tests for Parsoid as an extension
Change 612430 merged by jenkins-bot:
[integration/config@master] Turn on standard quibble tests for Parsoid as an extension
Change 612937 had a related patch set uploaded (by C. Scott Ananian; owner: C. Scott Ananian):
[integration/quibble@master] Load Parsoid as an extension when it is cloned into services/parsoid
Change 612937 merged by jenkins-bot:
[integration/quibble@master] Load Parsoid as an extension when it is cloned into services/parsoid
Ok, just waiting for another release of quibble to the CI infra. Watching https://github.com/wikimedia/quibble/commits/master ...
Change 628138 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/quibble@master] Release Quibble 0.0.45
Change 628138 merged by jenkins-bot:
[integration/quibble@master] Release Quibble 0.0.45
Change 701346 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[integration/config@master] Add parsoid dependency to VisualEditor
Change 703182 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):
[integration/quibble@master] Load Parsoid from vendor as fallback, and configure
Change 703182 merged by jenkins-bot:
[integration/quibble@master] Load Parsoid from vendor as fallback, and configure
Change 704936 had a related patch set uploaded (by Hashar; author: Hashar):
[integration/quibble@master] Release Quibble 1.0.0
Change 704936 merged by jenkins-bot:
[integration/quibble@master] Release Quibble 1.0.0
Mentioned in SAL (#wikimedia-releng) [2021-07-16T17:12:11Z] <hashar> Tag Quibble 1.0.0 @ a13d133f7d1 # T286187 T280506 T90875 T218534 T227352
Change 705907 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
[integration/quibble@master] Revert "Load Parsoid from vendor as fallback, and configure"
Change 705907 merged by jenkins-bot:
[integration/quibble@master] Revert \"Load Parsoid from vendor as fallback, and configure\"
Change 701346 abandoned by Hashar:
[integration/config@master] Add parsoid dependency to VisualEditor
Reason:
I am pretty sure this is obsolete nowadays. The last injections of parsoid got removed in July 2022 https://gerrit.wikimedia.org/r/c/integration/config/+/803990 .