+ # Step four: Delete snapshot artifacts from the local repository.
+ # This is critical to detect orphaned artifacts or missing project-internal dependency declarations.
+ # Also other files related to maven repository resolution are removed,
+ # and then empty directories are removed, in order to simplify debugging.
+ - shell: |
+ set +e # To avoid failures in projects which generate zero snapshot artifacts.
+ find /tmp/r/org/opendaylight/$GERRIT_PROJECT/ -path *-SNAPSHOT* -delete
+ find /tmp/r/ -regex '.*/_remote.repositories\|.*/maven-metadata-local\.xml\|.*/maven-metadata-fake-nexus\.xml\|.*/resolver-status\.properties' -delete
+ find /tmp/r/ -type d -empty -delete
+ echo "# INFO: A listing of project related files left in local repository follows."
+ find /tmp/r/org/opendaylight/$GERRIT_PROJECT/
+ true # To prevent the possibly non-zero return code from failing the job.
+ # Now the ugly part. It seems that the only way to tell Maven 2+
+ # which remote repositories to use is via settings.xml file.
+ # So we create such a file here, but it needs most of odlparent:settings.xml
+ - shell: |
+ echo '
+ <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+ https://maven.apache.org/xsd/settings-1.0.0.xsd">
+ <profiles>
+ <profile>
+ <id>opendaylight-release</id>
+ <repositories>
+ <repository>
+ <id>opendaylight-mirror</id>
+ <name>opendaylight</name>
+ <url>https://nexus.opendaylight.org/content/repositories/public/</url>
+ <releases><updatePolicy>never</updatePolicy></releases>
+ <snapshots><enabled>false</enabled></snapshots>
+ </repository>
+ </repositories>
+ <pluginRepositories>
+ <pluginRepository>
+ <id>opendaylight-plugin-mirror</id>
+ <name>opendaylight-plugin</name>
+ <url>https://nexus.opendaylight.org/content/repositories/public/</url>
+ <releases><updatePolicy>never</updatePolicy></releases>
+ <snapshots><enabled>false</enabled></snapshots>
+ </pluginRepository>
+ </pluginRepositories>
+ </profile>
+ <profile>
+ <id>file-snapshots</id>
+ <repositories>
+ <repository>
+ <id>file-snapshots</id>
+ <name>file</name>
+ <url>file:///tmp/n/</url>
+ <releases><enabled>false</enabled></releases>
+ </repository>
+ </repositories>
+ <pluginRepositories>
+ <pluginRepository>
+ <id>file-plugin-snapshots</id>
+ <name>file-plugin</name>
+ <url>file:///tmp/n/</url>
+ <releases><enabled>false</enabled></releases>
+ </pluginRepository>
+ </pluginRepositories>
+ </profile>
+ </profiles>
+ <activeProfiles>
+ <activeProfile>file-snapshots</activeProfile>
+ <activeProfile>opendaylight-release</activeProfile>
+ </activeProfiles>
+ </settings>
+ ' > fake_remotes.xml
+ # # Notes: The settings are minimal in order to detect breakage scenarios while allowing for the following quirks:
+ # # * Some plugins seem to have hardcoded repos, for example check-license looks at repository.apache.org
+ # # * Some plugin artifacts (related to surefire) are not downloaded when tests are skipped.
+ # # * populate-local-repo looks at oss.sonatype.org and does not store things (like guava) to /tmp/r
+ # Step five: Repeat the distribution build but with the new settings.
+ # Here, only the project snapshot artifacts deployed to /tmp/n are available,
+ # which faithfully reproduces conditions in later verify-like job runs.
+ # We cannot use --offline, because: "Cannot access file (file:///tmp/n) in offline mode"
+ # This is where SingleFeatureTest is not skipped.
+ - maven-target:
+ maven-version: 'mvn33'
+ pom: 'distribution/pom.xml'
+ goals: 'clean install dependency:tree -DoutputFile=dependency_tree.txt -s fake_remotes.xml -V -B -Pq -DskipTests=false -Djenkins -Dstream={stream} -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r'
+ java-opts:
+ - '-Xmx1024m -XX:MaxPermSize=256m -Dmaven.compile.fork=true'
+ # Step six: Run Karaf and verify no critical failures are present.