f2989df305
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.
28 lines
341 B
YAML
28 lines
341 B
YAML
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
|