Polymer CI Runner

A continuous integration test runner focused on web components. It accepts GitHub webhooks, coordinates a fleet of workers, and runs tests.

Configuring The Webhook

Through the joys of Firebase, you can have GitHub webhooks publish directly to it. Create a new webhook:

https://<your-firebase-app>.firebaseio.com/queue.json

You will want to turn on pull request and push status.

Running Locally

npm start

(Assuming that you have the correct environment variables set. See below.)

Spinning Up Your Own Workers

The CI runner is intended to be run as a persistent server. The worker is published as a Docker image that you can use; and we provide configuration to make that easy.

Google Compute Engine

You can make use of the tools/gcloud/manage script. You will need to create a .polymer-ci-runner.sh and place it somewhere handy.

At minimum, you need the following options specified:

# The Google Compute Engine project name.
export GCLOUD_PROJECT=my-ci-project

# OAuth token used when posting statuses/comments to GitHub.
# See https://github.com/settings/applications
export GITHUB_OAUTH_TOKEN=abcdef0123456789abcdef0123456789abcdef01
# The secret registered for the webhook; invalid requests will be rejected.
export GITHUB_WEBHOOK_SECRET=abcdef0123456789abcdef0123456789abcdef01

# Your Sauce Labs username.
export SAUCE_USERNAME=username
# Your Sauce Labs access key.
export SAUCE_ACCESS_KEY=abcdef01-abcd-abcd-abcd-abcdef012345

# The Firebase URL where queue entries and run statuses are stored under.
export FIREBASE_ROOT=https://my-firebase-app.firebaseio.com
# The Firebase secret used to generate an authentication token.
export FIREBASE_SECRET=abcdef0123456789abcdef0123456789abcdef01

You can then run manage from any directory that contains that config file directly, or up its path.

The full set of configuration values is specified in lib/config.js.