Gitlab.com CI for Private Projects

Summary: We have a concern based on one piece of documentation regarding Gitlab.com CI for private projects

Note: This is in reference to Gitlab.com (and not a self-hosted gitlab)

Concern: We came across this link, https://docs.gitlab.com/ee/ci/runners/#be-careful-with-sensitive-information

My Interpretation: its not advisable to build private projects in Default Gitlab CI Runners

• Is the interpretation valid? and to what extent a concern?
• What do you think will be the best practice for this?

Question:

Is it fine to use Gitlab.com Shared Runners for CI in Private Projects?

Our Solution: IF and only IF we need an alternative (POC for this was successfully implemented)

1. We created a EC2 Instance (a private box)
2. Installed Gitlab Runner to the box
3. Connected EC2 Instance to Gitlab
4. Disabled Shared Runner from Project setting
5. On CI run, it successfully sends the request to our EC2 instance