Size: 2882
Comment:
|
Size: 3504
Comment: Queue time score bumps are no longer a thing
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
~- [[FrontPage|Launchpad Help]] > [[Packaging]] > Prioristing builds -~ | ~- [[FrontPage|Launchpad Help]] > [[Packaging]] > Prioritising builds -~ |
Line 20: | Line 20: |
* time since upload to the queue * whether the package is destined for a public or private PPA. |
* package sets containing the package * archive containing the package * time the package has spent in the build queue |
Line 28: | Line 29: |
|| -proposed || 0 || || -backports || 1500 || || <release> || 3000 || || -updates || 4500 || || -security || 6000 || |
|| -backports || 0 || || <release> || 1500 || || -proposed || 3000 || || -updates || 3000 || || -security || 4500 || |
Line 56: | Line 57: |
=== Time in queue === | === Package sets === |
Line 58: | Line 59: |
Rather than allow low priority packages to linger in the queue for too long, Launchpad increases a build's priority according to its age. | 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: |
Line 60: | Line 61: |
|| '''Age''' || '''Score''' || || 300 seconds || 5 || || 900 seconds || 10 || || 1800 seconds || 15 || || 3600 seconds || 20 || || 7200 seconds || 50 || || 14400 seconds || 100 || |
|| '''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 || |
Line 69: | Line 74: |
=== Archive privacy === | === Archives === |
Line 77: | Line 82: |
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. |
|
Line 80: | Line 93: |
In some circumstances, Launchpad assigns a fixed score to builds: | 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: |
Line 82: | Line 95: |
* '''copy:''' builds that are actually copies from one archive to another get a fixed score of 4 * '''translation:''' builds for sources targeted to the ''transalation'' section get a fixed score of 0, 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. |
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.
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.