We have enough tests that the length of the builds is getting painful. Explore getting more builders in Jenkins from Cloudbees
Version: wmf-deployment
Severity: enhancement
We have enough tests that the length of the builds is getting painful. Explore getting more builders in Jenkins from Cloudbees
Version: wmf-deployment
Severity: enhancement
I do not think this is an easy bug (removing the keyword), since it probably involves money. :)
We could get more slaves attached to the Wikimedia server. It might not be cost effective though.
As I understand it, CloudBee is basically Jenkins as a service. It is being used to start the tests in instances hosted at SauceLabs.
We can most probably migrate the jobs to the Wikimedia Jenkins installation and have it trigger the jobs in SauceLabs.
Chris, should be close this as wontfix, since we will be moving Jenkins jobs from Cloudbees to WMF Jenkins soon?