All geek questions in one place

How to start using Gitlab-CI in the release of Gitlab Omnibus?

I installed Gitlab Omnibus gitlab-7.4.3_omnibus.5.1.0.ci-1.el6.x86_64.rpm on CentOS 6.6. I have several projects created and working perfectly, but I would like to try the continuous integration features. I don’t know where to start, but the documentation / textbooks are thin on the ground. I found the following files that do not appear in the old Gitlab omnibus installation. I have:

/usr/bin/gitlab-ci-rake /usr/bin/gitlab-ci-rails

I suppose I need to do something with this? But do I need a configuration file? In my projects (Settings> Services> Gitlab CI) I see that there are options for Active, Token and Project Url, but I don’t know what to put in these fields. Any help that helps me get started with CI will be greatly appreciated. Cheers, Jonny

+6
source share
1 answer

We recently installed the Omniubus GitLab 7.6.2 release with integrated GitLab CI 5.3. I had the same question. This is how we work it.

We use one secure server via https; single ip for gitlab and gitalb-ci hosts. We have DNS records for both host names for the same ip. (Done with an alias for the ci server, I think). We have two ssl certificates, one for each hostname.

We have the following lines at the top of the /etc/gitlab/gitlab.rb script (found by searching on the gitlab website for details on setting up the rb file):

 external_url 'https://gitlab.example.edu' nginx['redirect_http_to_https'] = true ci_external_url 'https://gitlab-ci.example.edu' ci_nginx['redirect_http_to_https'] = true

For http, leave nginx instructions.

If gitlab-ci url displays the contents of the gitlab site, then the ci_nginx instruction needs to be adjusted.

+4
source

Source: https://habr.com/ru/post/978396/

More articles:


All Articles