Gitlab CI is not starting?


Problem is solved. Gitlab CI doesn’t provide a separate website. CI is now fully integrated. See my comment below.

Although running: gitlab-ctl service-list still shows the ci-… services in the list… :worried:

After some frustration, researching I discovered that the CI webpage ( doesn’t exist anymore. I read that ci_external_url is even deprecated --> I only found this by looking up into the latest gitlab.rb.template file in some of your repositories :confused:… I have no idea how the domain is now used during the runner setup?
Nevertheless, it was also listed on the top of quick start page bleeh:

Note: Starting from version 8.0, GitLab Continuous Integration (CI) is fully integrated into GitLab itself and is enabled by default on all projects.

Although it is stated, in my opinion it could be more clean saying: “The CI website doesn’t exist anymore”.

Nevertheless, I logged in as ‘root’ user within Gitlab CE.

  1. I went to the following URL to get a token:
    Let’s say the token is: “blabla”.
  2. I installed docker:
    curl -sSL | sh
  3. Installed gitlab ci multirunner:
    curl -L | sudo bash
  4. Installing it:
    sudo apt-get install gitlab-ci-multi-runner
  5. Register the runner:
    sudo gitlab-ci-multi-runner register
  6. Enter the following info (apparently I can’t configure anymore? So by default is is
  7. So I did the following during register:
Please enter the gitlab-ci coordinator URL (e.g. )

Please enter the gitlab-ci token for this runner

Please enter the gitlab-ci description for this runner
Gitlab Runner

Please enter the gitlab-ci tags for this runner (comma separated):                                                                                                                                         production                                                                                                                                                              

Please enter the executor: shell, docker, docker-ssh, ssh?

Please enter the Docker image (eg. ruby:2.1):

Now I hopefully got a valid runner.

Finally I created a gitlab CI yml file in the root directory of a repository, named: .gitlab-ci.yml.
I’m using PHP Symfony framework, my file looks like:

  - export COMPOSER_CACHE_DIR=/cache/composer
  - composer install --no-interaction

    - bin/console cache:clear --env=prod
    - bin/console assetic:dump --env=prod
    - production

Although I need to install ‘composer’ application first on the docker image…

Bottom-line: The separate CI site doesn’t exist anymore. But should redirect to Why does this /ci still exists during the runner setup? How is that used?