GitLab
The all-in-one alternative: repository, merge requests, CI/CD, container and package registries, and security scanning inside one product. Interviews contrast it with GitHub and ask how the pieces meet: approval rules on the merge request, the job token that lets a pipeline reach the registry, and a scan finding that blocks the merge.
on this pageshowhide
explore
- Repositories and Merge Requests6 questions
- CI/CD Pipelines6 questions
- Hosted Runners and Fleet4 questions
- Registries and Packages6 questions
- Security Scanning6 questions
- Self-Managed vs SaaS6 questions
questions
page 2 of 2In GitLab, who can read the job logs and artifacts of a public project's pipelines, and which settings narrow that?
basics
~20 sOn a public GitLab project with Project-based pipeline visibility selected and CI/CD open to Everyone With Access, anyone can read pipelines, job logs and artifacts. Clearing that checkbox, or setting CI/CD to Only project members, keeps them to project members.
In GitLab 19.4, a project still includes Jobs/Dependency-Scanning.gitlab-ci.yml. Which analyzer runs, and how do you move it to SBOM-based scanning?
basics
~20 sThe stable template still runs the Gemnasium-based analyzer, deprecated since GitLab 17.9 and never migrated automatically. Switch the include to Jobs/Dependency-Scanning.v2.gitlab-ci.yml, remove overrides of the gemnasium-* jobs, and point anything that referenced them at the new dependency-scanning job.
In GitLab 19.4, a pipeline run by a Maintainer overwrote the release image tag v2.3.0; would protected or immutable container tags have prevented it, and how?
basics
~20 sA protected tag rule stops it only if its minimum push role is above Maintainer; an immutable tag rule (Ultimate, generally available since GitLab 18.10) stops anyone from overwriting or deleting an existing matching tag.
For a GitLab Self-Managed instance serving about 3,000 users, how do you decide between a standalone node with backups, the high-availability reference architecture and adding Geo?
basics
~20 sSize from peak requests per second, then decide availability separately: up to about 2,000 users GitLab recommends standalone with backups, from 3,000 users or critical uptime the HA architecture, and Geo only for site-level disaster recovery.
showing 31–34 of 34