Jump to: navigation, search

Difference between revisions of "Platform-releng-new-baseline"

Line 23: Line 23:
 
<p>
 
<p>
 
Update HEAD version of org.eclipse.releng.eclipsebuilder/eclipse/sdk.tests/*perf/vm.properties to reference the new database and configuration as applicable.</p>
 
Update HEAD version of org.eclipse.releng.eclipsebuilder/eclipse/sdk.tests/*perf/vm.properties to reference the new database and configuration as applicable.</p>
 +
 +
<p>Run new 3.3 baselines. Ensure that ref34.properties is updated after the baselines have completed so future builds have a baseline to compare against</p>

Revision as of 15:04, 7 August 2007

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 ref.properties script on build machine. With 3.4, we have pointed it to a new database - for example...

net://trelenggtk.ottawa.ibm.com;dbname=perfDb34


/home/users/releng/buildTools/eclipse.perf
-bash-3.00$
-bash-3.00$ cp ref33.properties ref34.properties
-bash-3.00$ pwd

Update to ref34.properties 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/vm.properties to reference the new database and configuration as applicable.

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