Generalise buildergroup status handling

Bug #506239 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
William Grant

Bug Description

Currently the builder status handlers in lib/lp/buildmaster/buildergroup.py are passed through to BuildQueue.updatebuild_* (except for BuilderGroup.updatebuild_WAITING).

updatebuild_WAITING then calls BuilderGroup.buildstatus_[OK|PACKAGEFAIL|DEPFAIL|CHROOTFAIL|BUILDERFAIL|GIVENBACK]

all of which need to be generalisable.

The plan is to consolidate all of updatebuild_* on the build behaviors, with BuilderGroup.updatebuild() going to IBuilder.updatebuild(). The BuilderGroup.buildstatus_* can be moved onto specific build (ie. soyuz.model.build.Build or SourcePackageRecipeBuild.).

We can do the refactoring in two steps, first leaving a BuilderGroup.updateBuild proxy so that all the tests will still pass, then a second branch which will refactor the tests appropriately.

Related branches

Changed in soyuz:
milestone: none → 10.01
assignee: nobody → William Grant (wgrant)
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in soyuz:
status: Triaged → Fix Committed
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.