Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'production/testScripts/configuration/streamSpecific.properties')
-rw-r--r--production/testScripts/configuration/streamSpecific.properties14
1 files changed, 7 insertions, 7 deletions
diff --git a/production/testScripts/configuration/streamSpecific.properties b/production/testScripts/configuration/streamSpecific.properties
index f76a976d..cc25a899 100644
--- a/production/testScripts/configuration/streamSpecific.properties
+++ b/production/testScripts/configuration/streamSpecific.properties
@@ -11,16 +11,16 @@ streamSpecificPropertiesTitle="Properties for 4.13.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://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
+previousReleaseLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S-4.12RC2-201906051800
# 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.11
+previousReleaseVersion=4.12RC2
# 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.11
+previousReleaseVersionRepo=4.12milestones
# 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://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
-baselinePerfVersion=R-4.11-201903070500
+baselinePerfLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S-4.12RC2-201906051800
+baselinePerfVersion=S-4.12RC2-201906051800
# TODO: could/should eventually "compute" label, from full version?
-baselinePerfVersionLabel=4.11
-baselinePerfBuildId=I20190307-0500
+baselinePerfVersionLabel=4.12
+baselinePerfBuildId=I20190605-1800
eclipse.perf.dbloc.value=//172.25.25.57:1527

Back to the top