See T100293#1422770
Seems like there is some jenkins ci infrastructure we could reuse for triggering running the browser tests, and maybe other parts of what we are building.
Outcomes:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T91669 Make browser tests voting for all repos of WMF deployed code | |||
| Resolved | zeljkofilipin | T55697 [EPIC] trigger browser tests from Gerrit (tracking) | |||
| Resolved | Jhernandez | T104315 [GOAL]: Set up testing environments that run browser tests on all patches. | |||
| Resolved | Jdlrobson | T100293 [EPIC] Run browser tests against every MobileFrontend/Gather patch | |||
| Duplicate | None | T104840 Spike [3 hours]: Coordinate with @dduvall to see what CI infrastructure we can use. |
Also talk to @yuvipanda about the https://github.com/wikimedia/labs-tools-gerrit-to-redis
To quote the man with the red hair from T101069 "So step 1 to getting the gerrit to redis type stuff (gerrit stream it is called) working is to create an account for your gerrit bot, and then I can give it the stream right. I've given your account this right already, so you can test it locally (run ssh -p 29418 gerrit.wikimedia.org gerrit stream-events). You just need to implement this as well for your bot, and process the JSON coming out of the ssh."