From: Vasek Sraier <git@vakabus.cz>
Date: Mon, 22 Feb 2021 08:54:22 +0000 (+0100)
Subject: CI: configure poetry to use pyenv
X-Git-Tag: v6.0.0a1~230
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d6bdbd2b149cce2815ccdc9cb1dd0d96ba47a5a2;p=thirdparty%2Fknot-resolver.git

CI: configure poetry to use pyenv
---

diff --git a/manager/.gitlab-ci.yml b/manager/.gitlab-ci.yml
index e920100e9..99f62b722 100644
--- a/manager/.gitlab-ci.yml
+++ b/manager/.gitlab-ci.yml
@@ -2,7 +2,7 @@ stages:
   - build
   - check
 
-image: $CI_REGISTRY/knot/knot-resolver-manager/devenv:latest
+image: registry.nic.cz/knot/knot-resolver-manager/devenv:latest
 
 # Ideally, the CI would build it's own container and use it afterwards. This workflow should be supported,
 # at least according to the GitLab documentation:
@@ -33,6 +33,7 @@ lint:
     policy: pull-push
   script:
     # run the actual tests
+    - poetry env use $(pyenv which python)
     - poetry install
     - npm install
     - ./poe check