Skip to content

[JENKINS-60893] Number of thread for webhook processing is hardcoded  #418

@jenkins-infra-bot

Description

@jenkins-infra-bot

The number of threads used for concurrent webhook processing is hardcoded to 10, but there are some scenarios where an administrator would like to increase or reduce this number.

For instance, I have several slow processes due to Bitbucket API rate limit. Once 10 of those processes are in progress, no other webhook is being processed (although those other processes would go quite fast because they are from a different user, they are waiting for ages because 10 slow requests are still running)


Originally reported by luispiedra, imported from: Number of thread for webhook processing is hardcoded
  • status: Open
  • priority: Major
  • component(s): scm-api-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251223-222157
Raw content of original issue

The number of threads used for concurrent webhook processing is hardcoded to 10, but there are some scenarios where an administrator would like to increase or reduce this number.

For instance, I have several slow processes due to Bitbucket API rate limit. Once 10 of those processes are in progress, no other webhook is being processed (although those other processes would go quite fast because they are from a different user, they are waiting for ages because 10 slow requests are still running)

environment
Jenkins 2.204.1<br/>
scm&#39;api&#39;plugin 2.6.3<br/>
branch-api-plugin 2.5.5

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions