launchpad help|
⇤ ← Revision 1 as of 2009-05-06 14:51:50
Size: 2997
Comment:
|
Size: 3017
Comment: Karl's improvements
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| When you upload a source package to Launchpad, it assigns the package a priority and then uses the priority to decide when the package should be sent to Launchpad's [[https://launchpad.net/builders|build-farm]]. | 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 [[https://launchpad.net/builders|build-farm]]. |
| Line 8: | Line 9: |
| Launchpad calculates the priority of the build based on its attributes. We call this the build's "score". The higher the score, the sooner the build is dispatched to one of the available build machines. | 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. |
| Line 63: | Line 64: |
| || '''Age [in seconds]''' || '''Score''' || || 300 || 5 || || 900 || 10 || || 1800 || 15 || || 3600 || 20 || || 7200 || 50 || || 14400 || 100 || |
|| '''Age''' || '''Score''' || || 300 seconds || 5 || || 900 seconds || 10 || || 1800 seconds || 15 || || 3600 seconds || 20 || || 7200 seconds || 50 || || 14400 seconds || 100 || |
Launchpad Help > Packaging > Prioristing 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
- time since upload to the queue
- whether the package is destined for a public or private PPA.
The build score is the sum of all the scores that Launchpad awards the build for each of these criteria.
Target pocket
Launchpad gives a higher score to builds depending on the importance of their target pocket.
Score |
|
-proposed |
0 |
-backports |
1500 |
<release> |
3000 |
-updates |
4500 |
-security |
6000 |
Target component
Launchpad gives a higher score to builds depending on the importance of their 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 |
Time in queue
Rather than allow low priority packages to linger in the queue for too long, Launchpad increases a build's priority according to its age.
Age |
Score |
300 seconds |
5 |
900 seconds |
10 |
1800 seconds |
15 |
3600 seconds |
20 |
7200 seconds |
50 |
14400 seconds |
100 |
Archive privacy
Builds destined for private PPAs are given a higher priority.
Privacy status |
Score |
public |
0 |
private |
10000 |
Other
Builds targeted to copy archive get a fixed score of 4, so even the least prioritized build will be dispatched before anything from COPY archives.
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.
