diff options
author | Sarika Sinha | 2019-06-19 05:27:08 +0000 |
---|---|---|
committer | Sarika Sinha | 2019-06-19 09:40:37 +0000 |
commit | 195bd4e8a25987e385ea1de7a9cb89096dcfcc56 (patch) | |
tree | f4ac10ff5f1ea35dec06fa818098fa199ee4a42d /production/testScripts/configuration | |
parent | 5243e3a1704373f7ad6afa2f3664c15b7d5f0a12 (diff) | |
download | eclipse.platform.releng.aggregator-195bd4e8a25987e385ea1de7a9cb89096dcfcc56.tar.gz eclipse.platform.releng.aggregator-195bd4e8a25987e385ea1de7a9cb89096dcfcc56.tar.xz eclipse.platform.releng.aggregator-195bd4e8a25987e385ea1de7a9cb89096dcfcc56.zip |
Bug 547925 - Move to release version of 4.12 in build scripts
Change-Id: I80f4bb35747460fb0ea00f80b598182a04d18f69
Diffstat (limited to 'production/testScripts/configuration')
-rw-r--r-- | production/testScripts/configuration/streamSpecific.properties | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/production/testScripts/configuration/streamSpecific.properties b/production/testScripts/configuration/streamSpecific.properties index cc25a8990..53f998192 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/S-4.12RC2-201906051800 +previousReleaseLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.12-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.12RC2 +previousReleaseVersion=4.12 # 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.12milestones +previousReleaseVersionRepo=4.12 # 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,8 +34,8 @@ 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/S-4.12RC2-201906051800 -baselinePerfVersion=S-4.12RC2-201906051800 +baselinePerfLocation=http://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.12-201906051800 +baselinePerfVersion=R-4.12-201906051800 # TODO: could/should eventually "compute" label, from full version? baselinePerfVersionLabel=4.12 baselinePerfBuildId=I20190605-1800 |