launchpad help|
Size: 3802
Comment: update to current code
|
Size: 3897
Comment: slightly more specific about package set handling
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 59: | Line 59: |
| Package sets are used in distributions to apply properties such as upload permissions to groups of packages. A package set may have a "relative build score" bonus assigned to it in the Launchpad database. Currently, package sets in the Ubuntu distribution that are used to build images receive bonuses as follows: | Package sets are used in distributions to apply properties such as upload permissions to groups of packages. A package set may have a "relative build score" bonus assigned to it in the Launchpad database, and a package receives the maximum of the bonuses for any of the package sets that contain it. Currently, package sets in the Ubuntu distribution that are used to build images receive bonuses as follows: |
Launchpad Help > Packaging > Prioritising builds
Prioritising builds
When you upload a source package to Launchpad, it assigns the package a priority -- a "score" -- and then uses that score to decide when the package should be sent to Launchpad's build-farm.
Launchpad calculates the score based on various attributes (described below). The higher the score, the sooner the build is dispatched to one of the available build machines.
There are separate build queues for distributions and PPAs.
How Launchpad calculates the score
Launchpad uses the following attributes of a package to calculate its priority:
target pocket -- e.g. security
target component -- e.g. universe
- source urgency -- defined by the packager
- package sets containing the package
- archive containing the package
- time the package has spent in the build queue
Launchpad adds up the scores from each category to decide the build's priority.
Target pocket
Score |
|
-backports |
0 |
<release> |
1500 |
-proposed |
3000 |
-updates |
3000 |
-security |
4500 |
Target component
Component |
Score |
multiverse |
0 |
universe |
250 |
restricted |
750 |
main |
1000 |
partner |
1250 |
Source urgency
A packager can specify the urgency of their source package. Launchpad takes this into account.
Urgency |
Score |
low |
5 |
medium |
10 |
high |
15 |
emergency |
20 |
Package sets
Package sets are used in distributions to apply properties such as upload permissions to groups of packages. A package set may have a "relative build score" bonus assigned to it in the Launchpad database, and a package receives the maximum of the bonuses for any of the package sets that contain it. Currently, package sets in the Ubuntu distribution that are used to build images receive bonuses as follows:
Package set |
Score |
core |
50 |
desktop-core |
50 |
edubuntu |
50 |
kubuntu |
50 |
lubuntu |
50 |
mythbuntu |
50 |
ubuntu-desktop |
50 |
ubuntu-server |
50 |
ubuntustudio |
50 |
xubuntu |
50 |
Archives
Builds destined for private PPAs are given a higher priority.
Privacy status |
Score |
public |
0 |
private |
10000 |
Builds destined for copy archives (used for test rebuilds of the Ubuntu primary archive) are given a lower priority.
Copy archive? |
Score |
yes |
-2600 |
no |
0 |
Archives may also have a "relative build score" bonus assigned to them in the Launchpad database.
Build queue time
Build scores increase the longer a package has spent in the queue.
Queue time |
Score |
less than 5 minutes |
0 |
5 to 15 minutes |
5 |
15 to 30 minutes |
10 |
30 to 60 minutes |
15 |
60 to 120 minutes |
20 |
120 to 240 minutes |
50 |
more than 240 minutes |
100 |
Other
In some circumstances, Launchpad assigns a fixed, low score to builds, meaning they will be processed only when there isn't anything else in the queue:
translation: builds for sources targeted to the translations section get a fixed score of 0.
