Problem Definition

Bamboo should have a separate, configurable and smaller default timeout for change detection operations. E.g. git ls-remote

Currently it is tied to the command timeout (Repository Configuration >> Advanced Options >> Command timeout) which defaults to 3hrs to accommodate large clones.

As an instance gets larger and responsibility of plans and repositories goes to smaller teams, often plans can become legacy and forgotten. Some repositories are no longer contactable or are migrated to different locations but some plans aren't updated. Long timeouts of operations which should complete in a timely fashion end up utilizing important Bamboo, limited threads for long periods of time and negatively impact the instance by creating large delays in triggering.

Suggested Solution

Have a separate, configurable and smaller default timeout for change detection operations.

All timeouts need to be clearly logged and identifiable in the application logs.

Considerations:

• Per repository? Global? Both?
• If Command Timeout is set to a value less than the Change Detection timeout, should it take precedence?