manual builds should take precedence over daily builds
Bug #585993 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Aaron Bentley | ||
Bug Description
Because manual builds are initiated by a user, that user will want output as soon as possible. Daily builds will be created all at once, and if they took precedence over manual builds, that could delay the manual builds considerably. Daily builds are not as time-sensitive, because the user did not request them directly, and may in fact be asleep when they are requested. Therefore, manual builds should take precedence, i.e. have a higher queue score.
Related branches
lp:~abentley/launchpad/daily-builds-score
- Paul Hummer (community): Approve (code)
-
Diff: 305 lines (+62/-26)13 files modifiedlib/lp/buildmaster/model/buildqueue.py (+9/-0)
lib/lp/code/browser/sourcepackagerecipe.py (+3/-9)
lib/lp/code/browser/tests/test_sourcepackagerecipe.py (+11/-4)
lib/lp/code/model/sourcepackagerecipe.py (+4/-1)
lib/lp/code/model/sourcepackagerecipebuild.py (+3/-0)
lib/lp/code/model/tests/test_sourcepackagerecipe.py (+20/-0)
lib/lp/code/model/tests/test_sourcepackagerecipebuild.py (+3/-5)
lib/lp/soyuz/doc/binarypackagebuild.txt (+1/-1)
lib/lp/soyuz/doc/buildd-dispatching.txt (+2/-2)
lib/lp/soyuz/doc/buildd-slavescanner.txt (+2/-1)
lib/lp/soyuz/model/publishing.py (+0/-1)
lib/lp/soyuz/stories/soyuz/xx-build-record.txt (+1/-1)
lib/lp/testing/factory.py (+3/-1)
| Changed in launchpad-code: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Aaron Bentley (abentley) |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| Changed in launchpad-code: | |
| milestone: | none → 10.06 |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-code: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r11004 <http://