Whenever we have a Jenkins slave in labs for browser testing, we will need to add it manually as a node of the main Jenkins installation.
Version: wmf-deployment
Severity: enhancement
Whenever we have a Jenkins slave in labs for browser testing, we will need to add it manually as a node of the main Jenkins installation.
Version: wmf-deployment
Severity: enhancement
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 | hashar | T56388 browsertests: setup Jenkins job | |||
Resolved | None | T56389 browsertests: add labs instance has a jenkins slave in gallium |
I have applied the necessary change on integration-selenium-driver (which will be puppetized by bug 54383) and added the slave in Jenkins: https://integration.wikimedia.org/ci/computer/integration-selenium-driver/
Ready to serve master!
CCing Željko Filipin on any continuous bug related to browsertests. Main tracking bug is: bug 53697, see https://bugzilla.wikimedia.org/showdependencytree.cgi?id=53697&hide_resolved=0