Deployment Priority
To organize the deployments, you can assign Priority at the time of creating a deployment. Priority is an optional field, and you can leave it blank. A blank value is treated as the lowest priority. Priority can be an integer value ranging from 1 to 10000, where 1 is treated as the highest priority and 10000 as the lowest priority.
How Deployment Priority Works
At the time of a delivery target activation (move out of pending) priority is checked and the delivery targets with highest priority in the queue will be picked up first.
Example
Consider the scenario given below in the table:
|
Deployments
|
Delivery Targets
|
Priority
|
|||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
A
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
10
|
|
B
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
|
|
C
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
|
|
D
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
4
|
Four deployments are created: A, B, C and D. Each has 10 delivery targets. Deployment A has priority 10 and D has priority 4. Deployments B and C do not have any priority; therefore it is left blank.
Then the priority is set like this:
A: 10
D: 4
B: None
C: None
If all Deployments are scheduled at the same time, then delivery targets are activated in the order D1...D10 > A1...A10 > B1...B10...C1...C10.
 |
If no priority or same priority is selected the order is defined by first come first serve (oldest first)
|
While all deployments are in the In-Progress state and the delivery targets are in the pending state, if the priority of B is changed from no priority to 5, then the order will become D1...D10 > B1...B10 > A1...A10 > C1...C10.