Skip to main content
diff options
Diffstat (limited to 'production/testScripts/configuration/')
1 files changed, 7 insertions, 7 deletions
diff --git a/production/testScripts/configuration/ b/production/testScripts/configuration/
index 4ef4be453..693ec628f 100644
--- a/production/testScripts/configuration/
+++ b/production/testScripts/configuration/
@@ -11,16 +11,16 @@ streamSpecificPropertiesTitle="Properties for 4.10.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.
# 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?
# 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
# 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.
# TODO: could/should eventually "compute" label, from full version?

Back to the top