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 6 as of 2009-07-14 16:50:16 → 
  Size: 2866
  Editor: 87-194-127-65
  Comment: Write time-in-queue times in more easily comprehensible units.
+   ← 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 20:
- * time since upload to the queue
-Line 28:
+Line 27:
-|| -proposed  ||   0  ||
|| -backports || 1500 ||
|| <release>  || 3000 ||
+|| -backports ||    0 ||
|| <release>  || 1500 ||
|| -proposed  || 3000 ||
-Line 56:
+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'''  || '''Score''' ||
|| 5 minutes  || 5   ||
|| 15 minutes || 10  ||
|| 30 minutes || 15  ||
|| 1 hour     || 20  ||
|| 2 hours    || 50  ||
|| 4 hours    || 100 ||
-Line 80:
+Line 66:
-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 68:
- * '''copy:''' builds that are actually copies from one archive to another get a fixed score of 4
 * '''translation:''' builds for sources targeted to the ''translation'' 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"