| James E. Blair | d78576a | 2013-07-09 10:39:17 -0700 | [diff] [blame] | 1 | Since 1.2.0: |
| 2 | |
| 3 | * The Jenkins launcher is replaced with Gearman launcher. An internal |
| 4 | Gearman server is provided, and there is a Gearman plugin for |
| 5 | Jenkins, so migration to the new system should be fairly |
| 6 | straightforward. See the Launchers section of the documentation for |
| 7 | details. |
| 8 | |
| James E. Blair | d047097 | 2013-07-29 10:05:43 -0700 | [diff] [blame] | 9 | * The custom parameter function signature has changed. It now takes a |
| 10 | QueueItem as the first argument, rather than the Change. The |
| 11 | QueueItem has the full context for why the change is being run |
| 12 | (including the pipeline, items ahead and behind, etc.). The Change |
| 13 | is still available via the "change" attribute on the QueueItem. The |
| 14 | second argument is now the Job that is about to be run, ande the |
| 15 | parameter dictionary is shifted to the third position. |
| 16 | |
| Jeremy Stanley | e6abe81 | 2013-07-31 21:14:16 +0000 | [diff] [blame^] | 17 | * The ZUUL_SHORT_* parameters have been removed (the same |
| James E. Blair | d047097 | 2013-07-29 10:05:43 -0700 | [diff] [blame] | 18 | functionality may be achieved with a custom parameter function that |
| 19 | matches all jobs). |
| James E. Blair | 6736beb | 2013-07-11 15:18:15 -0700 | [diff] [blame] | 20 | |
| 21 | * The default behavior is now to immediately dequeue changes that have |
| 22 | merge conflicts, even those not at the head of the queue. To enable |
| 23 | the old behavior (which would wait until the conflicting change was |
| 24 | at the head before dequeuing it), see the new "dequeue-on-conflict" |
| 25 | option. |