Modeling Project Releng/Releasing/Scheduled Releases

Want to set up automatic builds and subsequent promotes? You need to edit the apache's crontab on your build server to set a schedule.

For example, to run an I build every Tuesday at 6pm, and promote it two hours later:

# EMF 2.5 I builds from HEAD
00 18 * * 2 /home/www-data/build/emf/scripts/start_cron.sh -sub emf -buildType I -tagBuild true -runJDK50Tests -runJDK60Tests \
 -basebuilderBranch RC2_34 -a -email "nickboldt+build@gmail.com" -noSearchCVS > $HOME/cron_logs/start_cron.sh.emf.25I.txt 2>&1

00 20 * * 2 /home/www-data/build/modeling/scripts/promoteToEclipse_cron.sh \
 -c org.eclipse.emf/org.eclipse.emf.releng/scripts/promoteToEclipse.emf.properties,HEAD -sub emf -branch 2.5.0 -type I -user nickb \
 -announce -email "nickboldt+build@gmail.com" > $HOME/cron_logs/promoteToEclipse_cron.sh.emf.25I.txt 2>&1

Or, to listen to CVS for changes, then tag & release those changes to your map file(s), and run a build ONLY IF REQUIRED:

# GEF I builds: see gef.HEAD.options.txt#EXECUTE_ON_MAP_CHANGE for start_cron.sh command
00 19 * * 2 /home/www-data/modeling-releng-common/tools/org.eclipse.releng.tools.tagandrelease/update_tags.sh \
 /home/www-data/modeling-releng-common/tools/org.eclipse.releng.tools.tagandrelease/gef.HEAD.options.txt -debug 2 \
 > $HOME/cron_logs/update_tags.sh.gef.35I.txt 2>&1

00 20 * * 2 /home/www-data/build/modeling/scripts/promoteToEclipse_cron.sh -parent NONE \
 -d :pserver:anonymous@dev.eclipse.org:/cvsroot/tools -c org.eclipse.gef/org.eclipse.gef.releng/promoteToEclipse.gef.properties,HEAD \
 -sub gef -branch 3.5.0 -type I -user nickb -announce -email "nickboldt+build@gmail.com" \
 > $HOME/cron_logs/promoteToEclipse_cron.sh.gef.35I.txt 2>&1

More examples can be seen in the crontab for apache@emft.eclipse.org.

See also Scheduled Builds.