Ghost/ghost/admin/.travis.yml

sudo: required
dist: trusty

language: node_js
node_js:
  - "4"

env:
  global:
    - GITHUB_OAUTH_KEY=003a44d58f12089d0c0261338298af3813330949
    - JOBS=1 # See https://git.io/vdao3 for details.

branches:
  except:
    - /^greenkeeper-.+$/

cache:
  yarn: true
  directories:
    - $HOME/.npm
    - $HOME/.cache # includes bower's cache

addons:
  firefox: "latest"
  chrome: "stable"

before_install:
  # install latest yarn
  - curl -o- -L https://yarnpkg.com/install.sh | bash
  - export PATH=$HOME/.yarn/bin:$PATH

install:
  - yarn global add bower
  - yarn
  - bower install

before_script:
  - export DISPLAY=:99; sh -e /etc/init.d/xvfb start; sleep 3;

script:
  - COVERAGE=true npm test

after_success:
  - npm run coverage
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00			`sudo: required`
			`dist: trusty`

			`language: node_js`
			`node_js:`
Recommend Node v4 & use as default (#126) refs TryGhost/Ghost#7098 - Use Node v4 as our default build environment - Change engines in package.json to match Ghost core 2016-07-15 14:12:17 +03:00			`- "4"`
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00
add buildAboutPage task to Gruntfile (#90) 2016-06-28 20:36:00 +03:00			`env:`
			`global:`
			`- GITHUB_OAUTH_KEY=003a44d58f12089d0c0261338298af3813330949`
Bump dependencies (#887) no issue - ember/ember-data/ember-cli@2.16 - bump all outdated dependencies that do not require additional work or more extensive tests - bump sub-dependencies in yarn.lock - use `broccoli-uglify-sourcemap` (same dep as already used in `ember-cli-uglify`) instead of a separate `broccoli-uglify-js` package for building production codemirror assets - add `/concat-stats-for` to `.gitignore` so that filesize stats from `CONCAT_STATS=true ember build` don't end up in the repo 2017-10-12 18:42:10 +03:00			`- JOBS=1 # See https://git.io/vdao3 for details.`
add buildAboutPage task to Gruntfile (#90) 2016-06-28 20:36:00 +03:00
Add greenkeeper branch ignores to travis This prevents greenkeeper branches from being built as they will always by run in the PR. 2016-06-22 19:31:11 +03:00			`branches:`
Fix: travis exception for greenkeeper branches (#130) - travis terminology is inconsistent :( 2016-07-15 19:51:00 +03:00			`except:`
Add greenkeeper branch ignores to travis This prevents greenkeeper branches from being built as they will always by run in the PR. 2016-06-22 19:31:11 +03:00			`- /^greenkeeper-.+$/`
Add Gruntfile.js, setup linting task and Travis build refs #23 - add `grunt lint` - add lint build to Travis matrix 2016-05-24 15:07:31 +03:00
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00			`cache:`
Re-enable yarn in Travis no issue - we had [previously reverted](https://github.com/TryGhost/Ghost-Admin/commit/787646a4a235dc6740f6e2ae6b98c3c59e347fbc) the use of `yarn` on Travis as we suspected it as being a culprit in failing editor builds, that wasn't the real cause so this switches us back to using `yarn` 2017-02-19 17:36:07 +03:00			`yarn: true`
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00			`directories:`
Run Chrome in headless mode on Travis no issue - align Travis config more closely to default ember-cli setup - run Chrome in headless mode in CI (Travis + `ember test`, `ember test --server` is "dev" mode) - install yarn via install script rather than npm - remove broccoli cache from Travis cache (not sure it ever worked?) - remove forced node-sass install (no longer needed) - add `testem` as a top-level dep to force the latest version (ember-data is pinned at 1.15) 2017-09-02 12:19:07 +03:00			`- $HOME/.npm`
			`- $HOME/.cache # includes bower's cache`
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00
			`addons:`
			`firefox: "latest"`
Upgrade to Ember 2.15.0 no issue - bumped `ember`, `ember-cli`, `ember-data` and related dependencies - bumped yarn.lock sub-dependencies - use new public `router` service in place of the private `-routing` service 2017-09-01 15:46:25 +03:00			`chrome: "stable"`
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00
Run Chrome in headless mode on Travis no issue - align Travis config more closely to default ember-cli setup - run Chrome in headless mode in CI (Travis + `ember test`, `ember test --server` is "dev" mode) - install yarn via install script rather than npm - remove broccoli cache from Travis cache (not sure it ever worked?) - remove forced node-sass install (no longer needed) - add `testem` as a top-level dep to force the latest version (ember-data is pinned at 1.15) 2017-09-02 12:19:07 +03:00			`before_install:`
			`# install latest yarn`
			`- curl -o- -L https://yarnpkg.com/install.sh \| bash`
			`- export PATH=$HOME/.yarn/bin:$PATH`

Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00			`install:`
Re-enable yarn in Travis no issue - we had [previously reverted](https://github.com/TryGhost/Ghost-Admin/commit/787646a4a235dc6740f6e2ae6b98c3c59e347fbc) the use of `yarn` on Travis as we suspected it as being a culprit in failing editor builds, that wasn't the real cause so this switches us back to using `yarn` 2017-02-19 17:36:07 +03:00			`- yarn global add bower`
			`- yarn`
Add initial Travis config file no issue - basic testing of the admin client with both Chrome and Firefox 2016-05-19 15:03:39 +03:00			`- bower install`

			`before_script:`
			`- export DISPLAY=:99; sh -e /etc/init.d/xvfb start; sleep 3;`

			`script:`
✨ Add code coverage (#481) no issue - adds code coverage via ember-cli-code-coverage - add coverage and ember-cli-code-coverage deps 2017-01-10 02:00:12 +03:00			`- COVERAGE=true npm test`

			`after_success:`
			`- npm run coverage`