Skip to main content
Jump to: navigation, search


Document that describes how to implement a new baseline once a release is available

Branch the versions of org.eclipse.releng.basebuilder, org.eclipse.releng.eclipsebuilder, eclipseInternalBuildTools, eclipsePerformanceBuildTools and org.eclipse.releng to a name that indicates the new baseline - for example perf_33x

Update script on build machine. With 3.4, we have pointed it to a new database - for example...


-bash-3.00$ cp
-bash-3.00$ pwd

Update to in all.xml of eclipsePerfomanceBuildTools, and buildAll.xml of org.eclipse.releng.eclipsebuilder (both HEAD and perf_33x branch).

Update HEAD version of org.eclipse.releng.eclipsebuilder/eclipse/sdk.tests/*perf/ to reference the new database and configuration as applicable.

Run new 3.3 baselines. Ensure that is updated after the baselines have completed so future builds have a baseline to compare against

How to connect to the derby database from the command line

export JAVA_HOME=/builds/Cloudscape_10.0/ibm-jre-n142p/jre
export DERBY_HOME=/builds/db-derby-
export PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:$DERBY_HOME

cd /builds/db-derby-


create the perfDb37 database

ij version 10.4
ij> connect 'jdbc:derby:perfDb37;create=true';

ij> protocol 'jdbc:derby';
ij> connect to 'perfDb36';
ij> show tables;
ij> select * from guest.variation;

Ensure that the is the eclipse/buildsConfigs/sdk.tests/*/ refers to the new database name in both the HEAD and perf_36x branch. In the 3.7 stream builds this is perfDb37.

Update the eclipsebuilder performance generation call to point to a new data directory on the build machine, for example data/v37 instead of data/v36.

See [ij tutorial for more examples]

Back to the top