BuildQueue still tied to BuildPackageJob

Bug #499350 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Undecided
Muharem Hrnjadovic

Bug Description

BuildQueue and BuildQueueSet need some more work to become fully generic:
 * BuildQueueSet.calculateCandidates joins with BuildPackageJob.
 * BuildQueueSet.getForBuilds joins with BuildPackageJob.
 * buildqueue.py shouldn't be in the Soyuz source tree.

Some or all of this may already be being addressed as part of the work on bug 484819.

The getForBuilds method is apparently used only by Soyuz browser code. So it's not in its perfect place, but it probably won't hurt other work based on the generalized build farm.

description: updated
description: updated
Curtis Hovey (sinzui)
affects: launchpad → soyuz
Changed in soyuz:
assignee: nobody → Muharem Hrnjadovic (al-maisan)
tags: added: buildfarm
Changed in soyuz:
milestone: none → 10.01
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

The build candidate selection is definitely pertinent and still outstanding and there's also BuildQueue.specific_job that still needs some love.

I would like to suggest that we close this bug and offer to file a number of more specific ones in return.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Agreed.

Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

OK, I added bugs #503845, #503836 and #503839 to track the outstanding work items.

Changed in soyuz:
status: New → Won't Fix
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.