Search

Companies / GitLab / incidents

GitLab: Gitlab.com Pipeline failures when using inputs

Impact: majorStatus: resolvedStarted Resolved (7.6 h)4 updatesSource: status.gitlab.com (opens in new tab)

Affected components: CI/CD

Timeline of updates

  1. identified

    We've identified the root cause of pipeline creation failures affecting pipelines that use inputs since Nov 24, 11:00 UTC. A fix is in the process of being deployed and we're monitoring for resolution. More info here: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/213976

  2. identified

    We are in the process of deploying a fix for the pipeline creation issues. Our next update will follow deployment completion as we monitor the resolution. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20886

  3. identified

    We are currently testing a fix for the pipeline creation issues in our sandbox environment. We estimate that the fix will be deployed to the production environment in approximately three hours. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20886

  4. resolved

    The fix has been deployed to production. We are no longer seeing failures for pipelines that use inputs. This is now resolved. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20886

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON