turn artifact spot check back on - sonatype resolved their problem
Change-Id: I266bc4d4e49cb278b2ae41beed63f957c7fd0222
diff --git a/tools/build/check-uploaded-maven-artifacts b/tools/build/check-uploaded-maven-artifacts
index 7b8f003..05819f1 100755
--- a/tools/build/check-uploaded-maven-artifacts
+++ b/tools/build/check-uploaded-maven-artifacts
@@ -49,7 +49,8 @@
sha1 = repoResponse.headers['x-checksum-sha1']
if sha1 != expectedSha1:
- print 'SHA1 hash is wrong expected ' + expectedSha1 + ' but found ' + sha1
+ print 'SHA1 hash is wrong for ' + remoteUrl + ' expected ' + \
+ expectedSha1 + ' but found ' + sha1
sys.exit(1)
def checkArtifactsForComponent(version, name, component, buildRoot, repoRoot):
diff --git a/tools/build/onos-build-and-upload b/tools/build/onos-build-and-upload
index d308d99..0888cf6 100755
--- a/tools/build/onos-build-and-upload
+++ b/tools/build/onos-build-and-upload
@@ -27,8 +27,7 @@
onos-upload-bits
# spot check that uploaded artifacts are correct
- # RAM - these have suddenly disappeared - need to investigate further
- #check-uploaded-maven-artifacts $VERSION $ONOS_ROOT https://oss.sonatype.org/content/groups/staging
+ check-uploaded-maven-artifacts $VERSION $ONOS_ROOT https://oss.sonatype.org/content/groups/staging
# set the version strings to the next version
onos-snapshot ${NEXT_VERSION}