@@ -11,16 +11,16 @@ streamSpecificPropertiesTitle="Properties for 4.31.0 builds and tests"
1111# stable version of Eclipse, that is used, for example, for it's p2
1212# director, etc., so that "running the tests" is not actually using
1313# the "just built" versions.
14- previousReleaseLocation =https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S -4.30RC2-202311231700 /
14+ previousReleaseLocation =https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R -4.30-202312010110 /
1515# version here is "build label" ... in general form, the "middle" of archive name,
1616# such as "eclipse-platform-${previousReleaseVersion}-linux-gtk-x86_64.tar.gz
1717# Also used used in p2 testing?
18- previousReleaseVersion =4.30RC2
18+ previousReleaseVersion =4.30
1919# This is last segment of last release repo, such as in
2020# http://${ARCHIVE_HOST}/eclipse/updates/${previousReleaseVersion}
2121# NOTE: I am assuming the "composite" repo is suitable for p2. In theory,
2222# they might want the simple repo, such as at 4.4/R-4.4.1-201409250400
23- previousReleaseVersionRepo =4.30-I-builds
23+ previousReleaseVersionRepo =4.30
2424
2525# Note: API tests needs the _base_ of previous release, and also the previous service release
2626# Bug 378587 - update releng tests (data) to go work against previous release
@@ -34,12 +34,12 @@ apiTestsPreviousRefererenceWin32Filename=obsoleteAndNotUsed
3434# baselinePerf=true
3535# are specified. The baselinePerf will often be the same as "previous release", but
3636# not necessarily, so is not hard coded in assumptions.
37- baselinePerfLocation =https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/S -4.30RC2-202311231700
37+ baselinePerfLocation =https://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R -4.30-202312010110
3838# NOTE: value must match baselineCode in testScripts/updateTestResultsPages.sh
39- baselinePerfVersion =S -4.30RC2-202311231700
39+ baselinePerfVersion =R -4.30-202312010110
4040# TODO: could/should eventually "compute" label, from full version?
4141baselinePerfVersionLabel =4.30
42- baselinePerfBuildId =I20231123-1700
42+ baselinePerfBuildId =I20231201-0110
4343
4444# We currently set here, but would be better to compute this value
4545# by peeking in the "to be tested" tar file.
0 commit comments