Skip to main content
aboutsummaryrefslogtreecommitdiffstats
blob: f76a976df72bf2d11a54a4c1ba2288a2638bab75 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
#
# This properties file should contains items that are specific to the stream being tested.
# Note: I don't believe these are currently being used, as intended, but can/will be
# at some point.

# purely title or identifier for display, to help confirm right file
# is being retrieved and used.
streamSpecificPropertiesTitle="Properties for 4.13.0 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://${DOWNLOAD_HOST}/eclipse/downloads/drops4/R-4.11-201903070500
# 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
# 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

# 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
# Bug 380033 - temp fix to hard code 'archive.eclipse.org' for now
apiTestsPreviousBaseDLBaseURL=obsoleteAndNotUsed
apiTestsPreviousBaseWin32Filename=obsoleteAndNotUsed
apiTestsPreviousRefererenceBaseDLBaseURL=obsoleteAndNotUsed
apiTestsPreviousRefererenceWin32Filename=obsoleteAndNotUsed

# the following are not used in unit tests, only performance tests, when the variables
# 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
# TODO: could/should eventually "compute" label, from full version?
baselinePerfVersionLabel=4.11
baselinePerfBuildId=I20190307-0500

eclipse.perf.dbloc.value=//172.25.25.57:1527

# We currently set here, but would be better to compute this value 
# by peeking in the "to be tested" tar file. 
isMacAppLayout=true

Back to the top