From f079546a53329d64db3ffde9aad81c9fb22bf8f9 Mon Sep 17 00:00:00 2001 From: Thanh Ha Date: Fri, 17 Mar 2017 14:52:18 -0400 Subject: [PATCH] Temporary workaround for Nexus SNI issue This should be reverted once Sonatype has an updated nexus staging plugin for us. Trello: https://trello.com/c/VBeO8STM Change-Id: Ia7c0916d6b181bfd153183ea5defb39ed8f7b7d5 Signed-off-by: Thanh Ha --- jjb/autorelease/include-raw-autorelease-maven-deploy.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh index ecb4169a9..89506c191 100644 --- a/jjb/autorelease/include-raw-autorelease-maven-deploy.sh +++ b/jjb/autorelease/include-raw-autorelease-maven-deploy.sh @@ -18,7 +18,7 @@ mkdir -p m2repo/org/opendaylight/ # in cases where an internal ci system is using multiple NEXUS systems one for artifacts and another for staging, # we can override using ODLNEXUS_STAGING_URL to route the staging build to the 2nd server. # (most CI setups where a single Nexus server is used, ODLNEXUS_STAGING_URL should be left unset) -NEXUS_STAGING_URL=${ODLNEXUS_STAGING_URL:-$ODLNEXUSPROXY} +NEXUS_STAGING_URL=${ODLNEXUS_STAGING_URL:-"http://10.29.8.46:8081"} NEXUS_STAGING_PROFILE=${ODLNEXUS_STAGING_PROFILE:-425e43800fea70} NEXUS_STAGING_SERVER_ID=${ODLNEXUS_STAGING_SERVER_ID:-"opendaylight.staging"} -- 2.36.6