Maven is well installed on my gitlab-runner server. When executing mvn clean
directly on my repo it works, when running my pip
I hope you had figure out your question. I met the same question when I build my ci on my server.
I use the shell as the executer for my Runner. here are the steps to figure out.
if you had install maven on the runner server successfully, maybe it just successful for the root, u can check the real user for the ci process.
job1:
stage: test
script: whoami
if my case, it print gitlab-runner
, not the root
In this time, it print error as same as the Gitlab ci UI.
Add maven to PATH:
$ export M2_HOME=/usr/local/apache-maven/apache-maven-3.3.9
$ export M2=$M2_HOME/bin
$ export PATH=$M2:$PATH
You can include these commands in $HOME/.bashrc
Just add the maven docker image, add below line as first line:
image: maven:latest or image: maven:3-jdk-10 or image: maven:3-jdk-9
refer: https://docs.gitlab.com/ee/ci/examples/artifactory_and_gitlab/
I managed to fix the problem using this workaround:
script:
- $MAVEN_HOME/bin/mvn clean