Bug 541826 - Move previous version to 4.10 across build scripts

Change-Id: Id9cf518ef11ae51e71181bec8d48fea60900b2cf
Signed-off-by: Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com>

3 files changed, 9 insertions, 9 deletions

diff --git a/production/testScripts/configuration/sdk.tests/testScripts/runtests.sh b/production/testScripts/configuration/sdk.tests/testScripts/runtests.sh
index 8d92deb75..5f23f985d 100755
--- a/production/testScripts/configuration/sdk.tests/testScripts/runtests.sh
+++ b/production/testScripts/configuration/sdk.tests/testScripts/runtests.sh
@@ -50,7 +50,7 @@ then
   exit 1
 else
   echo "stableEclipseInstallation directory found, as expected, at ${stableEclipseInstallLocation}"
-  # should only be one tar file there, with a name similar to eclipse-platform-4.9-linux-gtk-x86_64.tar.gz 
+  # should only be one tar file there, with a name similar to eclipse-platform-4.10-linux-gtk-x86_64.tar.gz 
   # so for simplicity, we'll assume all is well and untar what ever we find. 
   tar -xf ${stableEclipseInstallLocation}/*tar.gz -C ${stableEclipseInstallLocation}
 fi
diff --git a/production/testScripts/configuration/streamSpecific.properties b/production/testScripts/configuration/streamSpecific.properties
index 80d9df84c..e42f1a76a 100644
--- a/production/testScripts/configuration/streamSpecific.properties
+++ b/production/testScripts/configuration/streamSpecific.properties
@@ -11,16 +11,16 @@ streamSpecificPropertiesTitle="Properties for 4.11.0 builds and tests"
 # stable version of Eclipse, that is used, for example, for it's p2
 # director, etc., so that "running the tests" is not actually using
 # the "just built" versions.
-previousReleaseLocation=http://${ARCHIVE_HOST}/eclipse/downloads/drops4/R-4.9-201809060745
+previousReleaseLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S-4.10RC2-201812060815
 # version here is "build label" ... in general form, the "middle" of archive name,
 # such as  "eclipse-platform-${previousReleaseVersion}-linux-gtk-x86_64.tar.gz
 # Also used used in p2 testing?
-previousReleaseVersion=4.9
+previousReleaseVersion=4.10RC2
 # This is last segment of last release repo, such as in
 #  http://${ARCHIVE_HOST}/eclipse/updates/${previousReleaseVersion}
 # NOTE: I am assuming the "composite" repo is suitable for p2. In theory,
 # they might want the simple repo, such as at 4.4/R-4.4.1-201409250400
-previousReleaseVersionRepo=4.9
+previousReleaseVersionRepo=4.10milestones
 
 # Note: API tests needs the _base_ of previous release, and also the previous service release
 # Bug 378587 - update releng tests (data) to go work against previous release
@@ -34,11 +34,11 @@ apiTestsPreviousRefererenceWin32Filename=obsoleteAndNotUsed
 # baselinePerf=true
 # are specified. The baselinePerf will often be the same as "previous release", but
 # not necessarily, so is not hard coded in assumptions.
-baselinePerfLocation=http://${ARCHIVE_HOST}/eclipse/downloads/drops4/R-4.9-201809060745
-baselinePerfVersion=R-4.9-201809060745
+baselinePerfLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S-4.10RC2-201812060815
+baselinePerfVersion=S-4.10RC2-201812060815
 # TODO: could/should eventually "compute" label, from full version?
-baselinePerfVersionLabel=4.9
-baselinePerfBuildId=I20180906-0745
+baselinePerfVersionLabel=4.10RC2
+baselinePerfBuildId=I20181206-0815
 
 eclipse.perf.dbloc.value=//172.25.25.57:1527
 
diff --git a/production/testScripts/updateTestResultsPages.sh b/production/testScripts/updateTestResultsPages.sh
index 570206653..68f780326 100755
--- a/production/testScripts/updateTestResultsPages.sh
+++ b/production/testScripts/updateTestResultsPages.sh
@@ -314,7 +314,7 @@ then
   RAW_DATE_START=$( date -u +%s )
 
   # TODO: avoid this hard coding of baseline value
-  baselineCode="R-4.9-201809060745"
+  baselineCode="S-4.10RC2-201812060815"
   # to get time stamp, first remove initial IMN:
   baselineForBuildSuffix=${buildId/[IMN]/}
   #Then remove final '-' in build id