Setting Sidekiq job size limits too low can cause silent failures in the CI/CD pipeline

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

Setting the Sidekiq job size limits too low can cause unexpected issues with the CI/CD pipeline. In one of the cases we encountered, this setting was inadvertently set to a low value (20) which caused only the first jobs in pipelines to run.

Proposal

Depending on the use case, it's possible that it can silently break the CI/CD pipeline of an instance so it might be good to consider either:

  • Set a minimum threshold to allow pipelines to still run (i.e. includes 0 or disabled mode),
  • improve the warning in the documentation and mention the impact of setting it too low, or
  • add a warning message in a project's pipeline page in case stages and jobs are blocked by this limit.

Intended users

Feature Usage Metrics

Does this feature require an audit event?

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖