GitLab Pipeline set to Public but Behaves Private

Question

I'm using GitLab for open-source projects, they are all configured with the same privacy settings.

One of my projects however is acting as if I have Pipelines set to Only Project Members, even though I have it set to Public with Everyone With Access.

As far as I know, all I should have to do is make Project visibility Public, and make sure Pipelines are enabled with Everyone With Access and that should be it, however I still cannot access it without being logged it on any browser nor download artifacts through wget.

From a non-authenticated session I can still browse the repository itself though and go through code etc etc.

Is there a setting I'm missing somewhere that might affect pipeline/artifact visibility?

Answer 1

Pipeline visibility depends on multiple settings in different locations.

It has to be set as public in Settings > CI/CD > General pipelines as well, otherwise it will not be publically accessible.

Visibility of pipelines

Pipeline visibility is determined by:

• Your current user access level.
• The Public pipelines project setting under your project’s Settings > CI/CD > General pipelines.

- https://docs.gitlab.com/ee/ci/pipelines/settings.html#visibility-of-pipelines