Investigating GitLab [LWN.net]

Investigating GitLab

Posted Dec 6, 2018 20:11 UTC (Thu) by himi (subscriber, #340)
In reply to: Investigating GitLab by laarmen
Parent article: Investigating GitLab

Our use of gitlab-ci is still quite immature, so there probably are things that we're missing or have misunderstood. In our defense, the documentation isn't great . . .

I understand the logic behind treating the CI config as part of the repository, tied to the code that it's testing, but the actual implementation is what's left me a bit frustrated.

to post comments

GitLab CI fork interaction and Samba

Posted Dec 8, 2018 8:52 UTC (Sat) by abartlet (subscriber, #3928) [Link]

In Samba, we have two files:
- .gitlab-ci.yml
- .gitlab-ci-private.yml

The second file references a tag called private, and includes the first.

On repositories with access to our private runners (we host on gitlab.com and use their shared runners where able) we just change the configured CI file, but this setting doesn't persist over a fork, so everyone else gets a subset by default.

Not perfect, but working pretty well so far.

Samba's own particular way of using GitLab is here: https://wiki.samba.org/index.php/Samba_CI_on_gitlab