Summary

Bamboo will continuously contact the Repository servers(like Bitbucket, SVN) for repository polling even if the plans are disabled or not active for the linked repository configured for the plans/plan branches. This happens even when repository servers are not in an active state.

This will cause performance issues in Bamboo. The plan exec threads will be busy for a long time and continuously ping the repository servers where the repository is stored, blocking other activities of plan exec threads like schedule triggering or other plan build triggering.

If a Bamboo instance has a large number of plans with repository polling triggers(for active or disabled plans), the plan exec thread keeps on executing the change detection on the repository for the repository polling trigger, which causes huge performance delays for other activities. Sometimes, other build triggers will not be executed at all because of this blocking.

Suggestion

1. Bamboo should not contact repository servers on the repository polling trigger if the plans/plan branches are disabled.
2. Maybe a separate new thread in Bamboo should handle repository polling change detection instead of plan exec threads, and not block other build trigger activities.