From 3c280a6b29202fbc927105a41e1c23590dcf57e3 Mon Sep 17 00:00:00 2001
From: Malaber <32635600+Malaber@users.noreply.github.com>
Date: Thu, 20 Jun 2019 20:28:53 +0200
Subject: [PATCH] Run tests in image built one step above using latest tag

This isn't optimal since theoretically there could be an image pushed
just between building and downloading again, but variables cannot be
used within gitlab-ci.yml so that is what we have to work with. If
variables get introduced, we should lock this to the current commit sha.
---
 .gitlab-ci.yml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 8db289f..4f9f414 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -16,10 +16,9 @@ kaniko:
 
 rails spec:
   stage: test
-  image: ruby:2.6.2
+  image: registry.gitlab.com/turniere/turniere-backend/test
   script:
-    - bundle install --path /cache
-    - bundle exec rails db:migrate RAILS_ENV=test
+    - bundle exec rails db:migrate
     - bundle exec rails spec
 
 kubernetes: