Do not leave staging repo open

Nexus does not publish a staging repo if the repo is left in the Open
state. Unfortunately this means we have to decide on what's more
important.

1) Automated tests can trigger immediately after autorelease produces
   new build.
2) Ability to add additional artifacts to a Maven repo (such as GPG
   signatures)

Case 1 can only work if we Close the Staging repo. Case 2 requires us to
leave the Staging repo in Open state so that we can push gpg signatures
up after the build completes.

The workaround for Case 1 is the manually launch the
integration-distribution test once Helpdesk manually makes the staging
repo available post build. Which makes something that used to be
automated to now be a manual task which isn't ideal either.

Change-Id: I00c210cec159c83e7d3badf16306586541e364dc
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>

diff --git a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
index f9acf7c532da1a55ec69aac7c11ed95d16daf587..41f344ff228b1df12d9983e20fd5819649488fbe 100644 (file)
--- a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
+++ b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh
@@ -13,10 +13,13 @@
 # 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
-if [ "${DATESTAMP}" == "false" ]
-then
-    SKIP_STAGING_CLOSE=true
-fi
+# 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