https://bugzilla.wikimedia.org/show_bug.cgi?id=56622
Web browser: ---
Bug ID: 56622
Summary: We need a way to do het-deploy in beta-labs for
Parsoid/VisualEditor testing
Product: Wikimedia
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: Quality Assurance
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Classification: Unclassified
Mobile Platform: ---
Currently en.wikipedia.beta.wmflabs.org runs master of VisualEditor and a
manually-synced version of Parsoid that is the same as production. This is
great for testing VE as to whether it's good to deploy into production, and had
served us reasonably well so far.
We can't just run Parsoid as master, because (a) Parsoid master is occasionally
not compatible with VisualEditor master for days or even weeks at a time as the
APIs change, and (b) unless Parsoid is going to be pushed live at the same time
as VisualEditor (and split into a het-deploy situation for the cluster's wmfX
vs. wmfX+1 deployment) we wouldn't know if VE and Parsoid were truly OK to go
out.
However, bug 56583 showed that we also need to test master (and ideally also
current production) of VisualEditor against *master* of Parsoid, in Labs, for
automated browser testing and so on before any code goes live.
Do we need en.wikipedia.beta.wmflabs.org to have
en-Parsoid-master-VE-master.wikipedia.beta.wmflabs.org and
en-Parsoid-master-VE-prod.wikipedia.beta.wmflabs.org duplicates? (Eww.)
Also, are there other teams who need their multiple independent components and
cross-dependencies? Wikidata, perhaps?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
