-
Notifications
You must be signed in to change notification settings - Fork 32
/
.travis.yml
65 lines (53 loc) · 1.89 KB
/
.travis.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
# Travis CI (MIT License) configuration file for https://connor-baer.github.io/summer.
# @link https://travis-ci.org/
# Ditch sudo and use containers.
# @link http://docs.travis-ci.com/user/migrating-from-legacy/#Why-migrate-to-container-based-infrastructure%3F
# @link http://docs.travis-ci.com/user/workers/container-based-infrastructure/#Routing-your-build-to-container-based-infrastructure
sudo: false
# Declare project language.
# @link http://about.travis-ci.org/docs/user/languages/ruby/
language: ruby
# Declare versions of Ruby to use. Use one decimal max.
# @link http://docs.travis-ci.com/user/build-configuration/
matrix:
fast_finish: true
include:
- rvm: '2.3.1'
gemfile: gemfile
env: LINT=1
- rvm: 'ruby-head'
gemfile: gemfile
allow_failures:
- rvm: 'ruby-head'
before_install:
- nvm install --lts=dubnium
# Use this to prepare your build for testing.
# e.g. copy database configurations, environment variables, etc.
# Failures in this section will result in build status 'errored'.
before_script:
# Install JavaScript dependencies.
- if [[ "$LINT" == "1" ]]; then yarn; fi
# Run test script commands.
# Default is specific to project language.
# All commands must exit with code 0 on success. Anything else is considered failure.
# Assume bundler is being used, therefore
# the `install` step will run `bundle install` by default.
script:
#!/usr/bin/env bash
# Build the website.
- bundle exec jekyll build
# Lint the JavaScript code.
- if [[ "$LINT" == "1" ]]; then yarn lint; fi
# Receive notifications for build results.
# @link http://docs.travis-ci.com/user/notifications/#Email-notifications
notifications:
email:
email:
deploy:
provider: pages
skip-cleanup: true
github-token: $GITHUB_TOKEN # Set in the settings page of your repository, as a secure variable
keep-history: true
on:
branch: master