Move from rpm push in merge to rpm push in integration 18/1818/2
authorEd Warnicke <eaw@cisco.com>
Wed, 29 Jun 2016 22:00:54 +0000 (17:00 -0500)
committerEd Warnicke <eaw@cisco.com>
Wed, 29 Jun 2016 22:07:23 +0000 (17:07 -0500)
commit8b61e9fe9cc3b46dc40340a25b710d5b67b04a49
treec70d5e3aeef13ab62cb2b481f57687192200bcda
parent228a3dd2c6fc5f43fd9d6e8589d0fce2ffa960db
Move from rpm push in merge to rpm push in integration

It turns out that doing rpm push in both merge and integration
job leads to collisions because they have two separate
sequences of BUILD_NUMBERs and those BUILD_NUMBERS are used
for the rpm release number.

So... this patch makes the merge job *stop* pushing rpms,
and should cause the integration job to trigger on both
vpp *and* honeycomb merge job success.

Change-Id: I12fe582ea8a1444096b86c214b3cd3c412bc7591
Signed-off-by: Ed Warnicke <eaw@cisco.com>
jjb/honeycomb/honeycomb.yaml