I can’t get debugging .gitlab-ci.yml working: I have a very basic .gitlab-ci.yml file containing a run tests job. When I run gitlab-runner exec docker 'run tests', there’s no output (even if I make the test fail. How can I make gitlab-runner actually run?
.gitlab-ci.yml:
image: azul/zulu-openjdk-debian:8
variables
DEBIAN_FRONTEND: "noninteractive"
before_script:
- apt-get update -y
- apt-get -qq -y install curl
- curl -fsSLo boot https://github.com/boot-clj/boot-bin/releases/download/latest/boot.sh && chmod 755 boot
stages:
- test
- deploy
check sources:
stage: test
script:
- boot check-sources
run tests:
stage: test
script:
- boot test
Well, that worked. I found out that it was lack of an : in the script. It would be nice to have feedback, being, that the yml file is not well-formatted.
However, there’s another issue: I have a failed test. Running it locally gives this:
$ boot test
Downloading https://github.com/boot-clj/boot/releases/download/2.5.2/boot.jar...
Running for the first time, BOOT_VERSION not set: updating to latest.
Retrieving boot-2.7.1.jar from https://clojars.org/repo/
Retrieving clojure-1.8.0.jar from https://repo1.maven.org/maven2/
#http://boot-clj.com
#Tue Mar 28 13:43:57 UTC 2017
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_VERSION=2.7.1
BOOT_CLOJURE_VERSION=1.8.0
It doesn’t seem to run the tests, or logging is not shown, but more importantly, it’s not failing on the tests, while clearly, (= 0 1) is not true.
It’s because it couldn’t find the empty resources directory which wasn’t pushed to gitlab ('cause it’s empty, which makes perfect sense)… However, again, there’s no feedback why something doesn’t work as expected. It really would help a lot to have that feedback. Anyway, got it solved. Thanks!