You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GitLab Provider continuously adds commit statuses for every reconciliation.
This happens only for projects with more than 20 jobs. The GitLab Provider code already has some logic to prevent adding a commit status if one already exists. Still, it only considers the first 20 commit statuses because it is a paginated request that defaults to 20.
The impact of this bug is quite heavy. Thousands of commit statuses considered "external jobs" in the GitLab UI have piled up, with every new job triggering some GitLab background processes, nearly bringing down our GitLab instance.
The text was updated successfully, but these errors were encountered:
mo-rieger
pushed a commit
to mo-rieger/notification-controller
that referenced
this issue
Dec 19, 2024
The GitLab Provider continuously adds commit statuses for every reconciliation.
This happens only for projects with more than 20 jobs. The GitLab Provider code already has some logic to prevent adding a commit status if one already exists. Still, it only considers the first 20 commit statuses because it is a paginated request that defaults to 20.
The impact of this bug is quite heavy. Thousands of commit statuses considered "external jobs" in the GitLab UI have piled up, with every new job triggering some GitLab background processes, nearly bringing down our GitLab instance.
The text was updated successfully, but these errors were encountered: