summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorZ.J. van de Weg <zegerjan@gitlab.com>2016-06-23 12:35:04 +0200
committerZ.J. van de Weg <zegerjan@gitlab.com>2016-09-06 12:54:22 +0200
commitf6f06eae967cd512c0c573449ce4bd3e177a0f90 (patch)
tree930acbb395f45df19109f9a8a31d244066f7e092 /.gitlab-ci.yml
parent52cc64a8a4dc224df9df85f7933f8922cf6cef24 (diff)
downloadgitlab-ce-f6f06eae967cd512c0c573449ce4bd3e177a0f90.tar.gz
Have CI test migration paths
This commit adds a job to the pipeline to test if migration on seed data works. Even though the seed data is not perfect, it does give more guarentees that this will succeed in the real world too. seed_fu is used instead of dev:setup to save some time, as they both generate the data in the same way, this should be fine.
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml16
1 files changed, 15 insertions, 1 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index be5614520a5..d0805125a42 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -248,6 +248,21 @@ bundler:audit:
script:
- "bundle exec bundle-audit check --update --ignore OSVDB-115941"
+migration paths:
+ stage: test
+ <<: *use-db
+ only:
+ - master@gitlab-org/gitlab-ce
+ script:
+ - git checkout HEAD .
+ - git fetch --tags
+ - git checkout v8.5.9
+ - 'echo test: unix:/var/opt/gitlab/redis/redis.socket > config/resque.yml'
+ - bundle install --without postgres production --jobs $(nproc) "${FLAGS[@]}" --retry=3
+ - rake db:drop db:create db:schema:load db:seed_fu
+ - git checkout $CI_BUILD_REF
+ - rake db:migrate
+
coverage:
stage: post-test
services: []
@@ -263,7 +278,6 @@ coverage:
- coverage/index.html
- coverage/assets/
-
# Notify slack in the end
notify:slack: