Experiment with "Checks" in Travis output (#1081)

* Run tests on CI

* Create a lint error on purpose

* Splits build into test and deploy stages

lint and test jobs will run in parallel and if both are successful
(and branch is master), deploy will run.

* Revert "Create a lint error on purpose"

This reverts commit 306c91c.

* Updating snapshot

* Run deploy only on master branch (not PRs)

* Use global deploy config item to avoid building on PRs

Author: andrewn

.travis.yml

@@ -16,8 +16,14 @@ before_install:
 
 install: true
 
-script:
-  - docker-compose exec -T app npm run test:ci --verbose
+jobs:
+  include:
+    - stage: test
+      name: "Linting"
+      script: docker-compose exec -T app npm run lint
+    - # stage name not required, will continue to use `test`
+      name: "Tests"
+      script: docker-compose exec -T app npm run test
 
 before_deploy:
   - docker-compose stop
@@ -26,7 +32,6 @@ before_deploy:
   - gcloud --quiet version
   - gcloud --quiet components update
   - gcloud --quiet components update kubectl
-
 deploy:
   - provider: script
     script: ./deploy.sh

package.json

@@ -13,7 +13,7 @@
     "build:server": "cross-env NODE_ENV=production webpack --config webpack/config.server.js",
     "build:examples": "cross-env NODE_ENV=production webpack --config webpack/config.examples.js",
     "test": "jest",
-    "test:ci": "npm run lint",
+    "test:ci": "npm run lint && npm run test",
     "fetch-examples": "cross-env NODE_ENV=development node ./server/scripts/fetch-examples.js",
     "fetch-examples-gg": "cross-env NODE_ENV=development node ./server/scripts/fetch-examples-gg.js",
     "fetch-examples-ml5": "cross-env NODE_ENV=development node ./server/scripts/fetch-examples-ml5.js",