diff options
Diffstat (limited to 'production/testScripts/configuration/streamSpecific.properties')
| -rw-r--r-- | production/testScripts/configuration/streamSpecific.properties | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/production/testScripts/configuration/streamSpecific.properties b/production/testScripts/configuration/streamSpecific.properties index dccec2b4d..c74fde495 100644 --- a/production/testScripts/configuration/streamSpecific.properties +++ b/production/testScripts/configuration/streamSpecific.properties @@ -5,22 +5,22 @@ # purely title or identifier for display, to help confirm right file # is being retrieved and used. -streamSpecificPropertiesTitle="Properties for 4.7.0 builds and tests" +streamSpecificPropertiesTitle="Properties for 4.7.1 builds and tests" # These "previousRelease" variables are primarily used to have a # 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.6.3-201703010400 +previousReleaseLocation=http://${ARCHIVE_HOST}/eclipse/downloads/drops4/R-4.7-201706120950 # 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.6.3 +previousReleaseVersion=4.7 # 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.6 +previousReleaseVersionRepo=4.7 # 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.6-201606061100 -baselinePerfVersion=R-4.6-201606061100 +baselinePerfLocation=http://${ARCHIVE_HOST}/eclipse/downloads/drops4/R-4.7-201706120950 +baselinePerfVersion=R-4.7-201706120950 # TODO: could/should eventually "compute" label, from full version? -baselinePerfVersionLabel=4.6 -baselinePerfBuildId=I20160606-1100 +baselinePerfVersionLabel=4.7 +baselinePerfBuildId=I20170612-0950 eclipse.perf.dbloc.value=//172.25.25.57:1527 |