The buildd-manager should scan each builder individually

Bug #583221 reported by Julian Edwards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Julian Edwards

Bug Description

The buildd-manager currently does a scan of the whole build farm in one fell swoop, every 5 seconds. If there's a failure at any point during the scan, it causes the scan to stop where it is and any remaining transactions are aborted.

Ideally, each builder should be scanned periodically in its own right. The current mass-scan is an artefact of the old slave scanner and the underlying model code.

We can re-architect the buildd-manager slightly so that there's a timer event for each builder and scan each on separately.

Related branches

Changed in soyuz:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Julian Edwards (julian-edwards)
tags: added: buildd-manager
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Changed in soyuz:
milestone: none → 10.08
tags: added: qa-needstesting
Changed in soyuz:
status: In Progress → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.