Rate limits on pipeline creation
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
You can set a limit so that users and processes can’t request more than a certain number of pipelines each minute. This limit can help save resources and improve stability.
For example, if you set a limit of 10
, and 11
requests are sent to the trigger API within one minute,
the eleventh request is blocked. Access to the endpoint is allowed again after one minute.
This limit is:
- Applied to the number of pipelines created for the same combination of project, commit, and user.
- Not applied per IP address.
- Disabled by default.
Requests that exceed the limit are logged in the application_json.log
file.
Set a pipeline request limit
To limit the number of pipeline requests:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Network.
- Expand Pipelines Rate Limits.
- Under Max requests per minute, enter a value greater than
0
. - Select Save changes.
- Enable
ci_enforce_throttle_pipelines_creation
feature flag to enable the rate limit.
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support