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
whether the package is destined for a public or private PPA.

Launchpad adds up the scores from each category to decide the build's priority.

Target pocket

Pocket	Score
-backports	0
<release>	1500
-proposed	3000
-updates	4500
-security	6000

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

Archive privacy

Builds destined for private PPAs are given a higher priority.

Privacy status	Score
public	0
private	10000

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:

copy: test rebuilds of the Ubuntu primary archive get a fixed score of -10.
translation: builds for sources targeted to the translations section get a fixed score of 0.

< Packaging

-  ⇤ ← Revision 1 as of 2009-05-06 14:51:50 → 
  Size: 2997
  Editor: 92-237-59-186
  Comment:
+   ← Revision 8 as of 2010-07-16 00:36:13 → ⇥
  Size: 2471
  Editor: c122-108-38-217
  Comment: Fix copy archive score; it's now -10, not 4.
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-~- [[FrontPage|Launchpad Help]] > [[Packaging]] > Prioristing builds -~
+~- [[FrontPage|Launchpad Help]] > [[Packaging]] > Prioritising builds -~
 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 16:
+Line 17:
- * target pocket -- e.g. security
 * target component -- e.g. universe
+ * target [[Glossary#pocket|pocket]] -- e.g. security
 * target [[Glossary#component|component]] -- e.g. universe
-Line 19:
+Line 20:
- * time since upload to the queue
 Line 22:
-The build score is the sum of all the scores that Launchpad awards the build for each of these criteria.
+Launchpad adds up the scores from each category to decide the build's priority.
 Line 26:
-Launchpad gives a higher score to builds depending on the importance of their target pocket.
-Line 29:
+Line 27:
-|| -proposed  ||   0  ||
|| -backports || 1500 ||
|| <release>  || 3000 ||
+|| -backports ||    0 ||
|| <release>  || 1500 ||
|| -proposed  || 3000 ||
-Line 37:
+Line 35:
-Launchpad gives a higher score to builds depending on the importance of their target component.
-Line 59:
+Line 55:
-=== 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 [in seconds]''' || '''Score''' ||
|| 300   || 5   ||
|| 900   || 10  ||
|| 1800  || 15  ||
|| 3600  || 20  ||
|| 7200  || 50  ||
|| 14400 || 100 ||
-Line 83:
+Line 66:
-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.
+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 85:
+Line 68:
-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.
+ * '''copy:''' test rebuilds of the Ubuntu primary archive get a fixed score of -10.
 * '''translation:''' builds for sources targeted to the ''translations'' section get a fixed score of 0.

launchpad help

Diff for "Packaging/BuildScores"