.gitlab-ci.yml

image: ruby:2.3

variables:
  JEKYLL_ENV: production

before_script:
  - bundle install

test:
  stage: test
  script:
  - bundle exec jekyll build -d test
  artifacts:
    paths:
    - test
  except:
  - master

pages:
  stage: deploy
  script:
  - bundle exec jekyll build -d public
  artifacts:
    paths:
    - public
  only:
  - master
Bump to Ruby 2.3 2016-04-05 21:15:23 +03:00			`image: ruby:2.3`

Update .gitlab-ci.yml and README.md to specify production Jekyll configuration If a user is using GitLab Pages it is most likely the user is using GitLab pages to publish a website not just stage a website that is published elsewhere. If a user is publishing a website with Jekyll, they (and Jekyll themes/plugins) will expect that JEKYLL_ENV=production. This commit provides that specification in `.gitlab-ci.yml`. An examination of the existing repository showed this should not result in any change to the current rendering of the website. However, the specification may be important for developers as explained in preceding commit. 2017-02-10 22:28:52 +00:00			`variables:`
			`JEKYLL_ENV: production`

			`before_script:`
			`- bundle install`

Add a test job 2016-04-05 21:19:30 +03:00			`test:`
			`stage: test`
			`script:`
Switch to using a Gemfile 2017-02-10 16:45:26 -06:00			`- bundle exec jekyll build -d test`
Add a test job 2016-04-05 21:19:30 +03:00			`artifacts:`
			`paths:`
			`- test`
			`except:`
			`- master`

Add .gitlab-ci.yml 2015-12-17 12:49:09 +01:00			`pages:`
Add a test job 2016-04-05 21:19:30 +03:00			`stage: deploy`
Add .gitlab-ci.yml 2015-12-17 12:49:09 +01:00			`script:`
Switch to using a Gemfile 2017-02-10 16:45:26 -06:00			`- bundle exec jekyll build -d public`
Add .gitlab-ci.yml 2015-12-17 12:49:09 +01:00			`artifacts:`
			`paths:`
			`- public`
			`only:`
Bump to Ruby 2.3 2016-04-05 21:15:23 +03:00			`- master`