]> git.ipfire.org Git - thirdparty/knot-resolver.git/commitdiff
CI: configure poetry to use pyenv
authorVasek Sraier <git@vakabus.cz>
Mon, 22 Feb 2021 08:54:22 +0000 (09:54 +0100)
committerAleš Mrázek <ales.mrazek@nic.cz>
Fri, 8 Apr 2022 14:17:51 +0000 (16:17 +0200)
manager/.gitlab-ci.yml

index e920100e9ef3c71ef33a80982bf4959ee4fa71d8..99f62b722b9257d7654ca225e083163c4270512e 100644 (file)
@@ -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