X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=jjb%2Fvtn%2Fvtn.yaml;h=9a50752c1dea55f695aa6ced9ad7ca95d4e88934;hb=1eb36a6e6682565b6811feeacc31cbfe49ab069c;hp=ab56d85815c4c9883146820092e6ae3a69d8e3be;hpb=93ffdcbe009d3a4d1c4a38a62043822125827bdd;p=releng%2Fbuilder.git diff --git a/jjb/vtn/vtn.yaml b/jjb/vtn/vtn.yaml index ab56d8581..9a50752c1 100644 --- a/jjb/vtn/vtn.yaml +++ b/jjb/vtn/vtn.yaml @@ -23,6 +23,7 @@ jdk: openjdk7 jdks: - openjdk7 + - openjdk8 - stable-lithium: branch: 'stable/lithium' jdk: openjdk7 @@ -105,7 +106,7 @@ - maven-target: maven-version: '{mvn33}' pom: 'pom.xml' - goals: 'clean install -V -Pintegrationtests,strictcheck,docs -Dvtn.build.jobs=2 -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r' + goals: 'clean install -V -Pintegrationtests,strictcheck,docs -Dvtn.build.jobs=2 -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r -Dstream={stream}' java-opts: - '-Xmx1024m -XX:MaxPermSize=256m' settings: '{vtn-settings}' @@ -170,10 +171,41 @@ maven: maven-name: '{mvn33}' root-pom: 'pom.xml' - goals: 'clean install -V -Pintegrationtests,strictcheck,docs -Dvtn.build.jobs=2 -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r -Dmerge' + goals: 'clean install -V -Pintegrationtests,strictcheck,docs -Dvtn.build.jobs=2 -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r -Dmerge -Dstream={stream}' maven-opts: '-Xmx1024m -XX:MaxPermSize=256m' settings: '{vtn-settings}' global-settings: '{odl-global-settings}' + post-step-run-condition: UNSTABLE + + postbuilders: + - conditional-step: + condition-kind: file-exists + condition-filename: deploy-site.xml + condition-basedir: workspace + + # The strategy here is intentional to run Maven site:deploy twice + # once using regular pom.xml to produce a staged-site which is + # then used by deploy-site.xml to push to Nexus. This is a + # workaround to Maven Site's default linking code which creates + # incorrect URLs for sites due to auto-detection assuming your + # project is configured in a certain way which ODL is not. + steps: + - maven-target: + maven-version: '{mvn33}' + pom: pom.xml + goals: 'site:deploy -Dstream={stream}' + java-opts: + - '-Xmx2g' + settings: '{vtn-settings}' + global-settings: '{odl-global-settings}' + - maven-target: + maven-version: '{mvn33}' + pom: deploy-site.xml + goals: 'site:deploy -Dstream={stream}' + java-opts: + - '-Xmx2g' + settings: '{vtn-settings}' + global-settings: '{odl-global-settings}' reporters: - findbugs @@ -272,7 +304,7 @@ parameters: - project-parameter: - project: 'integration' + project: 'integration/distribution' scm: - git-scm: @@ -482,7 +514,7 @@ maven: maven-name: '{mvn33}' root-pom: 'pom.xml' - goals: 'com.sonatype.clm:clm-maven-plugin:index -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r' + goals: 'clean install com.sonatype.clm:clm-maven-plugin:index -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r' maven-opts: '-Xmx4096m -XX:MaxPermSize=512m' settings: '{vtn-settings}' global-settings: '{odl-global-settings}'