Page MenuHomePhabricator

Spike [3 hours]: Coordinate with @dduvall to see what CI infrastructure we can use.
Closed, DuplicatePublic

Description

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:

  • Email & comment on [[the epic | T100293]] CI infrastructure could we reuse for our browser-test-running on every patch.

Event Timeline

Jhernandez raised the priority of this task from to High.
Jhernandez updated the task description. (Show Details)
Jhernandez moved this task to Needs Analysis on the Reading-Web-Sprint-51-YOLO board.
Jhernandez added a subscriber: Jhernandez.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 6 2015, 10:57 AM

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."

KLans_WMF renamed this task from Spike: Coordinate with @dduvall to see what CI infrastructure we can use. to Spike [3 hours]: Coordinate with @dduvall to see what CI infrastructure we can use..Jul 6 2015, 4:31 PM
KLans_WMF set Security to None.
KLans_WMF moved this task from Needs Analysis to To Do on the Reading-Web-Sprint-51-YOLO board.
KLans_WMF removed subscribers: Jdlrobson, yuvipanda.

I'll merge this with T101069