Files
meteor/circle.yml
Ben Newman fee86a0b17 Try not running a full meteor --get-ready before Circle CI tests.
In the ongoing struggle with Circle CI-specific test failures, the
preparatory `meteor --get-ready` has been a consistent point of failure,
before any real tests have the chance to run.

Using a lighter-weight command (meteor --help) that still does most of
what --get-ready did seems worth a try, though it might just defer
memory-intensive work until later, so we'll have to see what happens.
2017-05-22 16:40:33 -04:00

29 lines
913 B
YAML

checkout:
post:
# https://discuss.circleci.com/t/git-submodule-url-isnt-playing-nice-with-the-cache/549/3
- git submodule sync
- git submodule update --init --recursive || (rm -fr .git/config .git/modules && git submodule deinit -f . && git submodule update --init --recursive)
dependencies:
pre:
# https://github.com/meteor/docs/blob/version-NEXT/long-form/file-change-watcher-efficiency.md
- echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
cache_directories:
- "dev_bundle"
- ".meteor"
- ".babel-cache"
override:
# shouldn't take longer than 5 minutes
- ./meteor --help:
timeout: 300
environment:
METEOR_PRETTY_OUTPUT: 0
METEOR_DISABLE_OPTIMISTIC_CACHING: 1
TOOL_NODE_FLAGS: --expose-gc
test:
override:
- ./scripts/ci.sh :
parallel: true
timeout: 1200