Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Platform-releng/Obsolete/Platform-releng-basics"

m
(Basic overview of platform builds)
Line 12: Line 12:
 
0 20 * * 1,2,3,5,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
 
0 20 * * 1,2,3,5,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
 
0 20 * * 4,6 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
 
0 20 * * 4,6 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
 +
</pre>
 +
 +
3.5.x maintenance builds run from R3_5_maintenance branch of org.eclipse.releng
 +
<pre>
 +
0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse35x/runMBuild
 
</pre>
 
</pre>
  

Revision as of 15:03, 7 July 2009

Basic overview of platform builds

Integration builds are in crontab of build user on build machine

Integration builds run from the tags of org.eclipse.releng

0 8 * * 2 cd /builds; /home/users/releng/buildTools/eclipse36/runIBuild-skipPerf

Nightly builds run from HEAD of org.eclipse.releng

0 20 * * 1,2,3,5,0 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf
0 20 * * 4,6 cd /builds; /home/users/releng/buildTools/eclipse36/runNBuild-skipPerf

3.5.x maintenance builds run from R3_5_maintenance branch of org.eclipse.releng

0 8 * * 3 cd /builds; /home/users/releng/buildTools/eclipse35x/runMBuild

The test machines for these builds are

ejwin1 (winxp with 1.5 vm)
ejwin2 (winxp with 1.5 vm
ejlnx1 (RHEL 5.3 with 1.5 vm)
ejlnx2 (RHEL 5.3 with 1.6 vm)
epwin2 (winxp with 1.5 vm)
eplnx1 (SLES 10 with 1.6 vm)
eplnx2 (RHEL 5.2 with 1.6 vm)
trelenggtk (database machine)
godel (cvs test machine)
eclipsebuildserv (build machine)

The windows tests machines crash every so often. They can just be rebooted and logged into as the build user. The event logs don't indicate that anything is wrong with the build.

A script runs once a week to clean the test machines

0 18 * * 0 /home/users/releng/buildTools/scripts/buildblaster.sh


Older builds 3.4.2 test builds run from tags in 3.4.x maintenance branch

cd /builds;  /home/users/releng/buildTools/eclipse34x/runKimTestMBuild

3.2.x test builds

cd /builds; /home/users/releng/buildTools/eclipse32x/runMTestBuild-skipPerf

Back to the top