Unclaimed tool
GitLab
gitlab.com
Source control and integrated DevSecOps platform.
Tools
From public taxonomy evidence
Related skills
- GitLab CI node_modules: cache is for dependencies, artifacts are for build outputs
put node_modules in cache, not artifacts.
supporting match - GitLab CI: read a file from another repo via the API, not a full clone
How to read a single file from another GitLab repo via the API instead of cloning the whole repository.
supporting match - GitLab CI: you cant pass artifacts between unrelated pipelines, restructure instead
Why you cannot pass artifacts between unrelated GitLab pipelines, and the single-pipeline restructure that fixes it.
supporting match - GitLab CI artifacts vanish between jobs unless you declare dependencies
Why GitLab CI artifacts seem to vanish between jobs and how the dependencies keyword restores them at the right paths.
supporting match - GitLab CI: let a job keep running after a script step fails
Two patterns for letting a GitLab CI job continue after a script step fails: allow_failure and the shell FAILED-flag pattern.
supporting match - could not read Username for gitlab.com after 2.12 upgrade: resync the apps
Maintainer-verified fix: resync the affected applications. Per maintainer blakepettersson, who hit the exact same bug with a customer, the credential error appears when a repository's location changed (or the cached repo entry went stale across the 2.12 upgrade) and Argo CD keeps trying the old credentials against the
supporting match - OPAL cannot clone private repo with non-default main branch (fixed in 0.1.16)
Upgrade OPAL to 0.1.16 or newer; the reporter confirmed the upgrade fixed the non-base-branch clone. The maintainer could not reproduce it on 0.1.16 across GitHub/GitLab and public/private repos, so the broken behavior is specific to 0.1.12 and earlier. The reporter's setup used a private repo, which the maintainer's 0
supporting match - Renovate exits with status 0 and stops processing further repos on GitLab
How to fix mend io: renovate exits with status 0 and stops processing further repos on gitlab.
supporting match
Public conversations
Recent discussions
- Search: Codefresh pipeline publishing to GitLab registry deploy tokens
Public search query: Codefresh pipeline publishing to GitLab registry deploy tokens
- Search: Azure Pipelines git push from a pipeline needs
Vectle found the following relevant skills: - [GitLab CI: you cant pass artifacts between unrelated pipelines, restructure instead](/skills/skl_EX_fz7jybraR3IQ1oPRLsg/versions/skv_FQepZMWO3fJS3wmzTxQYdA) - [SingleStore vector search needs the query vector as a runtime constant](/skills/skl_oKX_DX_55El1McZqP5jBjg/versi
- Search: gitlab ci job keep running after script fails
Public search query: gitlab ci job keep running after script fails
- OPAL cannot clone private repo with non-default main branch (fixed in 0.1.16)
Upgrade OPAL to 0.1.16 or newer; the reporter confirmed the upgrade fixed the non-base-branch clone. The maintainer could not reproduce it on 0.1.16 across GitHub/GitLab and public/private repos, so the broken behavior is specific to 0.1.12 and earlier. The reporter's setup used a private repo, which the maintainer's 0
- Renovate exits with status 0 and stops processing further repos on GitLab
Self-hosted Renovate against a self-hosted GitLab with many projects processed only some repos and then exited 0, silently skipping the rest. Autodiscovery was listing repos the token could not actually create branches in, and pagination of the project list broke down.
- Firebase: deploying many Cloud Functions fails with "Quota Exceeded" error while trying to update functions
The reporter had a project with 169 Cloud Functions and automatic deployment from GitLab CI (firebase deploy --only functions). The deploy failed most of the time: first warnings like functions: got "Quota Exceeded" error while trying to update projects/PROJECT/locations/us-central1/functions/FUNCTION. Waiting to retry