W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2018

CI Systems [was: Re: A new GitHub organization for web-platform-tests]

From: James Graham <james@hoppipolla.co.uk>
Date: Tue, 3 Apr 2018 21:54:50 +0100
To: public-test-infra@w3.org
Message-ID: <b62ffdab-a099-1fa6-f3a1-f80d4c1823b8@hoppipolla.co.uk>
On 30/03/2018 11:08, Philip J├Ągenstedt wrote:
> On Thu, Mar 29, 2018 at 7:20 PM James Graham <james@hoppipolla.co.uk> wrote:

> A bit more off-topic still, my hope is that we'll have the capacity to run
> all tests for every PR which touches resources/ or tools/ on at least some
> browsers, and that those long-running jobs would be separate status checks
> with no connection to Travis
FWIW I opened a PR some time ago [1] that would run all the tests on 
each commit to master in Firefox and Chrome nightly on Taskcluster [2]. 
We could certainly also use it (with a little effort) to run some per-PR 

Obviously as a system TC isn't perfect, but it does have a number of 
advantages over Travis that could make it a good complementary system:

* Much higher available capacity
* Docker-based for greater flexibility and ease of debugging
* Possible to write a "decision task" that programmatically schedules 
jobs based on the changeset or anything else.

(Some of the most obvious disadvantages include:
* Not as widely used
* More effort to get the jobs running since docker requires setup and 
the configuration is more transparently a shell script rather than the 
travis thing of a .yml file that is converted to shell commands 
providing high-level features)

[1] https://github.com/w3c/web-platform-tests/pull/9226
[2] https://docs.taskcluster.net/
Received on Tuesday, 3 April 2018 20:55:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 April 2018 20:55:18 UTC