GitLab CI - build a project in an infinite wait state

Question

I have problems with GitLab CI. I followed the official guide: https://github.com/gitlabhq/gitlab-ci/blob/master/doc/installation.md

Everything was fine, no mistakes anywhere. I also followed Runner-Setup. Everything is good.

But...

When I add a runner to a project and then try to build nothing, it happens. Maybe I didn’t quite understand something, or some of my configs are wrong. I am completely new to GitLab CI, but I like it and I want to learn new things.

I would be very happy if someone could help me.

Thanks!

MORE UPDATE: Just realized that:

~/gitlab-runners/gitlab-ci-runner$ bin/runner 

Starting the runner process manually solves the problem, but if I look at gitlab-ci-runner in /etc/init.d →, it works!?!

 ~/gitlab-runners/gitlab-ci-runner$ sudo /etc/init.d/gitlab-ci-runner start Number of registered runners in PID file=1 Number of running runners=0 Error! GitLab CI runner(s) (gitlab-ci-runner) appear to be running already! Try stopping them first. Exiting. ~/gitlab-runners/gitlab-ci-runner$ sudo /etc/init.d/gitlab-ci-runner stop Number of registered runners in PID file=1 Number of running runners=0 WARNING: Numbers of registered runners don't match number of running runners. Will try to stop them all Registered runners=1 Running runners=0 Trying to stop registered runners...kill: No such process OK Trying to kill ghost runners...OK 

What is wrong here? Am I not in power or do not see a problem ?!

Answer 1

The problem is solved!

You need to edit some values ​​in the /etc/init.d/gitlab-ci-runner script!

 APP_ROOT="**PATH_TO**/gitlab-runners/gitlab-ci-runner" APP_USER="**USER_WITH_DIRRIGHTS!**" PID_PATH="$APP_ROOT/tmp/pids" PROCESS_NAME="ruby ./bin/runner" RUNNERS_PID="$PID_PATH/runners.pid" RUNNERS_NUM=1 # number of runners to spawn START_RUNNER="nohup bundle exec ./bin/runner" 

Now it works!

Answer 2

In my case, the tags in runner were different from the tags in .gitlab-ci.yml. As soon as I changed them, those runner tags included all the tests of the configuration files, the tasks started to work.