BuildQueue.specific_job needs refactoring so it can cope with multiple build farm job types
Bug #503839 reported by
Muharem Hrnjadovic
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Muharem Hrnjadovic |
Bug Description
It's currently geared towards binary builds.
Related branches
lp:~al-maisan/launchpad/spec-job-class-503839
Merged
into
lp:launchpad
- Michael Nelson (community): Approve (code)
- Björn Tillenius: Pending (code) requested
-
Diff: 182 lines (+114/-3)4 files modifiedlib/lp/soyuz/configure.zcml (+10/-0)
lib/lp/soyuz/interfaces/buildqueue.py (+4/-0)
lib/lp/soyuz/model/buildqueue.py (+22/-3)
lib/lp/soyuz/tests/test_buildqueue.py (+78/-0)
Changed in soyuz: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Muharem Hrnjadovic (al-maisan) |
tags: | added: buildfarm |
Changed in soyuz: | |
status: | Confirmed → Triaged |
Changed in soyuz: | |
status: | Triaged → In Progress |
Changed in soyuz: | |
milestone: | none → 10.01 |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Furthermore, for the purpose of implementing general build farm infrastructure like job dispatch time estimation and candidate job selection we need a way of iterating over all build farm job classes.