Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
1
-
Description
Issue
Due to the way Quiet Periods are implemented, one of Bamboo's plan execution threads is consumed for the duration of the period.
Plan execution threads are limited to 4 by default, so if quiet periods are set for long periods of time (e.g. 10 seconds is the default, but users have been known to set values upwards of 5 or 10 minutes) then these "sleeping" jobs can potentially fill up the plan execution queue. This can result in an builds backing up in the queue, manual builds failing to start in a reasonable amount of time, etc
Suggestion
- As a Bamboo administrator, I would like to review thrown REST API how Repository Configuration >> Change detection options are set up so I can prevent Bamboo from running out of resources. For that, it would be interesting having:
- GET /rest/plugin/1.0/repository/changeDetection
Exposing a list of repositories and Change detection options - GET /rest/plugin/1.0/repository/<repositoryId>/changeDetection
Exposing given repository and Change detection options
- GET /rest/plugin/1.0/repository/changeDetection
- As a Bamboo administrator, I would like to review this configuration settings through the Support Tools