ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #gitlab
Reproducibility gap across GitLab CI/CD runners A team using GitLab CI/CD wants identical job execution environments across multiple runner hosts so that the same commit produces the same artifacts regardless of which runner picks up the job. The .gitlab-ci.yml image keyword accepts registry tags or Docker-style digests, and include: project can reference an
Goal Ensure that the combined database connection pools used by GitLab Rails/Puma, Sidekiq workers, and Workhorse never exceed the PostgreSQL server’s max_connections limit, preventing intermittent connection pool exhaustion under load. Constraints and uncertainty Each component exposes its own pool setting: gitlab_rails['db_pool'] , sidekiq['db_pool'] , and
I created a custom docker image and push it to docker hub but when I run it in CI/CD it gives me this error. exec /usr/bin/sh: exec format error Where : Dockerfile FROM ubuntu:20.04 RUN apt-get update RUN apt-get install -y software-properties-common RUN apt-get install -y python3-pip RUN pip3 install robotframework .gitlab-ci.yml robot-framework: image: ret
GitLab CI/CD variables marked as Masked are hidden from job logs through a string-replacement mechanism that targets the exact stored value. When a job script transforms that value—for example, piping a secret through base64 or embedding it in a JSON payload—the transformed representation no longer matches the original variable string and can appear in plain
Integration Boundary Question The GitLab backend API stores and returns all timestamps in UTC (ISO‑8601 with a ‘Z’ suffix), while the web UI converts these values to the authenticated user’s preferred time zone using client‑side JavaScript. Consumers of the API—such as CI/CD scripts, external dashboards, or custom integrations—must perform their own conversi
A small monolithic application hosted on GitLab needs to be migrated to a new version with zero downtime. The goal is to rely on a supported GitLab feature rather than custom scripts. The application already uses Auto DevOps for CI/CD, and the progressive deployment strategy offered by Auto DevOps is being considered. Questions: How can progressive deploymen
Context Gitter's REST API v1 enforces per-token rate limits for authenticated requests using GitLab personal access tokens with the api scope. The documentation states that authenticated requests allow higher throughput than unauthenticated ones, but exact quotas (requests per minute, burst allowance) are not published and may change without notice. Uncertai
Goal Maintain artifacts for downstream pipelines while respecting the configured expiration period. Constraints & Uncertainty GitLab allows expiration to be set globally, per-pipeline, or per-job. It is unclear whether artifacts referenced by downstream jobs are exempt from the same expiration rules or if they inherit the same policy as the originating j
Investigate how GitLab's configured API rate‑limit ceiling influences overall CI/CD pipeline throughput when max concurrent pipelines is adjusted. The default user‑level limit of 1000 requests per minute, configurable per instance via the rate_limit setting, interacts with pipeline concurrency controls under admin settings. When pipeline execution generates
docker
gitter