Index: buildtest/branches/2.0/adaptors/specjbb2000/adaptor.xml
===================================================================
--- buildtest/branches/2.0/adaptors/specjbb2000/adaptor.xml (revision 0)
+++ buildtest/branches/2.0/adaptors/specjbb2000/adaptor.xml (revision 0)
@@ -0,0 +1,62 @@
+
+
+
+
+
+
+
+
+
+ ${suite.name} setup
+
+
+
+
+ ${suite.name} run
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ${suite.name} clean
+ ${suite.name} clean does nothing.
+
+
+
+
Index: buildtest/branches/2.0/adaptors/specjbb2000/parameters.xml
===================================================================
--- buildtest/branches/2.0/adaptors/specjbb2000/parameters.xml (revision 0)
+++ buildtest/branches/2.0/adaptors/specjbb2000/parameters.xml (revision 0)
@@ -0,0 +1,42 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: buildtest/branches/2.0/adaptors/specjbb2000/readme.txt
===================================================================
--- buildtest/branches/2.0/adaptors/specjbb2000/readme.txt (revision 0)
+++ buildtest/branches/2.0/adaptors/specjbb2000/readme.txt (revision 0)
@@ -0,0 +1,24 @@
+This file describes implemetation of a runner of SPECjbb2000 benchmark which
+uses Build & Test Infrastructure 2.0 (HARMONY-3501).
+
+This readme assumes that the reader is already familiar with BT 2.0 concepts.
+
+It is assumed also that the one who wants to run SPECjbb2000 has the SPEC
+itself installed somewhere. The path to the SPEC location should be provided
+as a value to the parameter 'specjbb2000.spec.home'. Customization of SPEC
+execution is performed through editing of the props file, which is pointed
+by 'specjbb2000.prop.file' _optional_ parameter. By default this parameter
+points to '${specjbb2000.spec.home}/SPECjbb.props' file. By default, the
+SPEC will be executed with '-Xmx512m -Xms512m' options passed. This is
+configurable by _optional_ parameter named 'memory'.
+
+There are two notification options available - if an optional parameter
+'always.mail' is set to 'true', notifications are being sent after each run;
+if the parameter is set to 'false', only changes between passed/failed
+state are reported.
+
+The notification contains obtained score in the case of normal SPEC finish,
+and the whole log if the score were not obtained. Invalid scores are also
+treated as normal execution since this automation is intended for catching
+of functional regressions, not for precise performance measurements.
+