Do not leave staging repo open

[releng/builder.git] / jjb / autorelease / include-raw-autorelease-maven-deploy.sh

diff --git a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
index 402b90a4e0944b5345e9e9fc49534d9f3165f298..41f344ff228b1df12d9983e20fd5819649488fbe 100644 (file)
--- a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
+++ b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
@@ -9,6 +9,18 @@
 # http://www.eclipse.org/legal/epl-v10.html
 ##############################################################################
 
+# Job will pass in a variable ${DATESTAMP} if this variable is false than we
+# we are likely releasing a release candidate. We should skip closing the
+# Nexus staging repository so that we can sign the artifacts.
+SKIP_STAGING_CLOSE=false
+# TODO: Figure out a solution to Open staging repos not being available
+#       immediately. This means integration tests cannot reliably download and
+#       test the new build if we leave the staging repo open.
+# if [ "${DATESTAMP}" == "false" ]
+# then
+#     SKIP_STAGING_CLOSE=true
+# fi
+
 mkdir -p hide/from/pom/files
 cd hide/from/pom/files
 mkdir -p m2repo/org/opendaylight/
@@ -32,6 +44,7 @@ rsync -avz --exclude 'maven-metadata-local.xml' \
            "/tmp/r/org/opendaylight/integration" m2repo/org/opendaylight/
 
 mvn org.sonatype.plugins:nexus-staging-maven-plugin:1.6.2:deploy-staged-repository \
+    -DskipStagingRepositoryClose=${SKIP_STAGING_CLOSE} \
     -DrepositoryDirectory="`pwd`/m2repo" \
     -DnexusUrl=http://nexus.opendaylight.org/ \
     -DstagingProfileId="425e43800fea70" \