.travis.yml - Issue 1205043002: Enable Chrome Canary tests on Travis

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: .travis.yml

Issue 1205043002: Enable Chrome Canary tests on Travis (Closed) Base URL: https://github.com/dart-lang/dev_compiler.git@master

Patch Set: Created 5 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
1 language: dart	1 language: dart

2 sudo: false	2 sudo: false

3 dart:	3 dart:

4 - dev	4 - dev

5 - stable	5 - stable

6 before_install:	6 before_install:

7 - pub global activate dart_coveralls	7 - pub global activate dart_coveralls
	Jennifer Messerly 2015/06/24 15:44:22 we may want to move these into a script at some po we may want to move these into a script at some point? seems alright now though, hard to complain about a 20 line file :) vsm 2015/06/24 17:19:55 This might be useful if we want to automatically g Show quoted text On 2015/06/24 15:44:22, John Messerly wrote: > we may want to move these into a script at some point? > seems alright now though, hard to complain about a 20 line file :) This might be useful if we want to automatically get the latest canary rather than rely on user installation (for our own local runs). I'll leave it here for now though.
	8 - export CHROME_URL=https://storage.googleapis.com/chromium-browser-snapshots/ Linux_x64

	9 - export CHROME_REV=$(curl -s ${CHROME_URL}/LAST_CHANGE)

	10 - curl ${CHROME_URL}/${CHROME_REV}/chrome-linux.zip --create-dirs -o out/chrom e-linux.zip

	11 - unzip out/chrome-linux.zip -d out

	12 - export CHROME_CANARY_BIN=$PWD/out/chrome-linux/chrome

	13 - export DISPLAY=:99.0

	14 - sh -e /etc/init.d/xvfb start

	15 before_script:

	16 - npm install
	Jennifer Messerly 2015/06/24 15:44:22 I think this is normally the "install" step: http: I think this is normally the "install" step: http://docs.travis-ci.com/user/customizing-the-build/#Customizing-the-Install... not sure it matters, or what the difference is between before_install and install. vsm 2015/06/24 17:19:55 I tried to redo the steps to better match that (an Show quoted text On 2015/06/24 15:44:22, John Messerly wrote: > I think this is normally the "install" step: > http://docs.travis-ci.com/user/customizing-the-build/#Customizing-the-Install... > > not sure it matters, or what the difference is between before_install and > install. I tried to redo the steps to better match that (and tested on the karma branch).
8 script:	17 script:

9 - ./tool/presubmit.sh	18 - ./tool/presubmit.sh

	19 - ./node_modules/karma/bin/karma start --single-run
	Jennifer Messerly 2015/06/24 15:44:22 should this be part of presubmit? should this be part of presubmit? vsm 2015/06/24 17:19:55 I wanted to make you guys could run it first. :-) Show quoted text On 2015/06/24 15:44:22, John Messerly wrote: > should this be part of presubmit? I wanted to make you guys could run it first. :-)
10 - ./tool/coverage.sh	20 - ./tool/coverage.sh

OLD	NEW

« no previous file with comments | « no previous file | karma.conf.js » ('j') | karma.conf.js » ('J')