Age | Commit message (Collapse) | Author | Files | Lines |
|
* honeycomb-merge-master-ubuntu1404 needs java 8 for sonar
* the revert to java 7 happens prior to the sonar run
* we now throw the guest away after each use, so there is no need to
revert to java 7
Change-Id: I551a5a6d3da5eb9d38cc1f624ef547815a41931c
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
* honeycomb-merge-master-ubuntu1404 needs java 8 for sonar
* the revert to java 7 happens prior to the sonar run
* we now throw the guest away after each use, so there is no need to
revert to java 7
Change-Id: I82583ae4f6130961fb5c42741107ac74f80dd850
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
To deploy site into docs.fd.io
Works on top of:
https://gerrit.fd.io/r/#/c/3073/
Site distribution configuration:
https://gerrit.fd.io/r/#/c/3073/5/common/honeycomb-parent/pom.xml
... only Ubuntu14 deploys the site during merge job
Note: using site instead of site:site, since only with site we
can hook in groovy maven plugin to fix some generated links. With
site:site, the groovy maven plugin does not get executed.
Change-Id: Ie1086b8d20856dbe15992e67ccc0d15547ce56d3
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
Change-Id: I3d246666a3180e35d787c0350755804531e6f1d2
Signed-off-by: Vanessa Rene Valderrama <vvalderrama@linuxfoundation.org>
|
|
No need, sonar analysis is run on merge jobs. No need to run again
from integration job. Also integration jobs might be run even if honeycomb
code hasen't changed, running the analysis pointlessly.
Change-Id: I527dbc77e9ce528da169443a77f47f5251216670
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
According to
http://stackoverflow.com/questions/15596522/sonar-analysis-using-multiple-git-branches-in-jenkins
this is the way of telling sonar to distinguish analysis for
multiple branches.
Change-Id: I599f69a3cc00d7c7541a182b0604bfb74df6b158
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
Triggers are succes on merge jobs for VPP or HC.
The template was bad though. It used {branch} instead
of {stream} in job name. But all jobs are defined using
{stream}. This works for master since master branch and stream
names are identical, but not for 1609 stable/1609.
Change-Id: Iaf7888bcfadb481fff51051eaee87e7613fd7a78
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
Change-Id: Iea3e23f53c327c35a50bb415a23dc733c0bada26
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
Change-Id: I9d7614eb4d0586ba42d1156d119c68e8bac285a1
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|
|
* The script fails, though the failure can be ignored.
http://askubuntu.com/questions/599105/using-alternatives-with-java-7-and-java-8-on-14-04-2-lts
Change-Id: Ie7b70fb189505a46b6640f1a961001f0c75a21b5
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
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>
|
|
* remove deprecated MaxPermSize argument from mvn
* add repo-name parameter to job template definition
Change-Id: Ic202a8cbf56df52970c22996980206ce3849e1a3
Signed-off-by: C.J. Collier <cjcollier@linuxfoundation.org>
|
|
Change-Id: I7e792a561e8bf45f7b011b4dd85a69b96db4361d
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
|
|
Change-Id: Ia3a342e96349fc7c3cfd7448fce3e20e957bebff
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I33ab63dc4870054253d8310c5fbc381e786e05f5
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I13e35fcaf764db0c81dc335c0adb7e31ce7f8f42
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Iebb012635d1eb2d428c6859d4cf6d7d962203995
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I3c2a3650f30bd5d2bd49df30e78c57c5eb6d2ca8
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I0d341f1cc96c3d8a35a127f7cd6f667126dac9d7
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: If0c4bfaf9aeb650b5fb13f4c1ac64bc4919b7c5f
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Ibf5610b0607001178791bd9b56bcd0427e5ffee8
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I10da36d45ff8ea3d4b5c3a17e68d5ee89d3132de
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I1dd82bb2a8c5f7c19aa8905a24133e5805f31ae2
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Ie1f34c60b256588281e70b835b7bbd797265db3a
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
This patch depends on the merging of https://gerrit.fd.io/r/#/c/1574/
which must merge before it.
Please also note, while there is a first step to getting the package
pushing scripts into a common sharable place, the vpp script
for pushing has *intentionally* not been changed to use
it yet because of the release later this week as a matter
of risk management.
Change-Id: Ifad185d35f582a62bb750ece3c022a24d2153b4e
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
The configuration is based on information from:
http://docs.openstack.org/infra/jenkins-job-builder/builders.html
and
http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins#AnalyzingwithSonarQubeScannerforJenkins-Job-levelConfiguration
This setting should be tested on the actual infrastructure.
Change-Id: I7416c84881d8cf36330f81318e178140dbce755b
Signed-off-by: Tibor Frank <tifrank@cisco.com>
|
|
|
|
|
|
JJB 1.5.0 now allows CFP to use freeform IDs so lets use it to simplify
the yaml configuration.
Change-Id: Id64e772cb9fc1ed2f0deb11b6ba405f4ab43fe1e
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
|
|
Change-Id: Id91f825463bad7d8f48bb2efe1c5ac300e06a45e
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I911e6f366b4831dc87523b6b0529353f233f0791
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Perhaps 'Default' was the name at one point and then got renamed to
'Primary' and we forgot to update the configuration. Default is not
currently a valid server-name so resulted in Gerrit Trigger not watching
any valid Gerrit instance for the event-stream.
The current name of the Gerrit server-name is 'Primary' as defined in
Jenkins > Manage Jenkins > Gerrit Trigger.
Change-Id: Ic9481b53424d6fc8358131d384157779a7753fb0
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
|
|
Change-Id: Ie5fe2507b760b3f681be4291f9c52bf609dbfaca
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Ifbe5962e0161ccf223baa4bb4fc03f8c86d859b1
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Ib4381c10763251105ca1fc418e70c0e06905ba9a
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: I72afb24d177b3b81e9427d43c3adb4a0a80fd240
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Because we need the up-to-date vpp-japi.jar, its important
to rebuild when vpp rebuilds that jar.
Change-Id: Ifdfc93cd4274be1ceb8f92a5daf9084b9d9ed174
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Espcially the aggressive archive artifacts.
Change-Id: Ia20cfddb2ee543f000ca4d99f0462be7a740b608
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
I can't keep working on this anymore today and leaving it configured for
zuul overrnight is a broken concept.
This moves everything back to Gerrit Trigger control. We can move jobs
individually tomorrow.
Change-Id: I6943708a6001acb7c5acfe6a6746d6c056813f52
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
|
|
Change-Id: I055731ac99ae40960ee1e6a3e5cf0595d8da4600
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
|
|
Change-Id: I2f9eb1ce744881da675551bef420e1ccbbf172bf
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
honeycomb was mispelled and we hadn't caught that previously.
Change-Id: Ib33a61b1297a4afa246d33c3091298c20999373c
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
|
|
Change-Id: I50e3c7534ade3f241848df5896190038d3cc3410
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|