Do not run packer merge jobs concurrently

We probably should not allow packer merge jobs to run concurrently as
there's no benefit to doing so and can cause confusion on which image is
the latest. Like all existing merge jobs they should run in sequence.

Change-Id: Idc7d7bdf4a966e605120dd2aa0db80a381addf46
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>

diff --git a/jjb/releng-jobs.yaml b/jjb/releng-jobs.yaml
index e554f84f1476fee58276bb63fe7f746552139251..5c670819831d8f96f6755292ecc7789a62bc7e70 100644 (file)
--- a/jjb/releng-jobs.yaml
+++ b/jjb/releng-jobs.yaml
@@ -440,7 +440,6 @@
     name: 'builder-merge-packer-{platforms}-{templates}'
     project-type: freestyle
     node: centos7-java-builder-2c-4g
-    concurrent: true
 
     properties:
         - opendaylight-infra-properties: