Pipeline visibility in Internal projects for users who are not project members
Summary
There seems to be a mismatch between what the docs state related to pipeline visibility in Internal projects for users who are not project members.
The reference sections from our docs are:
- Change which users can view your pipelines
- Change pipeline visibility for non-project members in public projects
- GitLab CI/CD permissions
At the moment it is not clear if the mismatch is due to a bug, because the documentation is not up to date, or both.
This issue is related to the Zendesk support ticket #396426(internal only).
If the following is set:
- Public pipelines: Active
- CI/CD feature visibility: Everyone With Access
User can:
- View and access the
Pipelines
section in the left-side menu - View the Pipeline list
- View details for a Pipeline
- View details for a job
- Download job artifacts
User cannot:
- View job output
Expected: Based on the following statement from our docs
When it is selected, pipelines and related features are visible:
- For Internal projects, to all authenticated users except external users.
The user should only be able to view job outputs as well.
Steps to reproduce
- Create a new project and set the visibility to
Internal
. - Configure the Public pipelines option under
Settings > CI/CD
and the CI/CD feature underSettings > General > Visibility, project features, permissions
for the desired scenario. - Log in as a user who is not member of the project and check what is vizible.
Example Project
GitLab.com has the Internal
visibility disabled.
What is the current bug behavior?
The user cannot view output and logs for Internal Projects when Pipelines are Public and Visibility is Everyone can access
What is the expected correct behavior?
The user is able to view output and logs but not download job artifacts for Internal Projects when Pipelines are Public and Visibility is Everyone can access
Expand for output related to GitLab environment info
sudo gitlab-rake gitlab:env:info System information System: Ubuntu 20.04 Proxy: no Current User: git Using RVM: no Ruby Version: 3.0.5p211 Gem Version: 3.2.33 Bundler Version:2.3.15 Rake Version: 13.0.6 Redis Version: 6.2.8 Sidekiq Version:6.5.7 Go Version: go1.13.8 linux/arm64 GitLab information Version: 15.10.0-ee Revision: defe6e7f882 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 13.8 URL: http://gitlab-local.io HTTP Clone URL: http://gitlab-local.io/some-group/some-project.git SSH Clone URL: git@gitlab-local.io:some-group/some-project.git Elasticsearch: yes Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 14.18.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
Results of GitLab application Check
Expand for output related to the GitLab application check
sudo gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 14.18.0 ? ... OK (14.18.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 2/1 ... yes 4/2 ... yes 4/3 ... yes 4/6 ... yes 4/7 ... yes Redis version >= 6.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (3.0.5) Git user has default SSH configuration? ... yes Active users: ... 4 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... yes (elasticsearch 8.6.2) All migrations must be finished before doing a major upgrade ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Proposal
Update the permissions for internal projects when Everyone can access and Pipelines are Public to include viewing job output and logs