(To save time, create the Nightly job, then copy it to produce the Integration build, passing in slightly different parameters like BUILDTYPE = N or BUILDTYPE = I.)

Next, ssh to build.eclipse.org using your committer id and type crontab -e to create crontab entries which match the frequency of your N and I builds. In this example, the latest Nightly VE build will be published every day at 15h40 EST. The latest Integration will be published every Tuesday at 16h00 EST. Note that the promote.xml is identical, but the properties file differs.

In the N build properties file, we use "add" mode to incrementally publish N builds as they happen. In the I properties file, we use "replace" mode to scrub any accumulated builds and publish only the latest I build. So, once a week, we automatically purge the old garbage and get a fresh build.

In addition to publishing your zips, the promote.xml script also unpacks your Update zip into the path you specify, so you will have a daily/weekly up to date update site.

Specifying Source Directory

Your promote.*.properties file needs to define the parent folder in which to find a build folder. For example:

If more than one match is found, the newest directory by name (most recent build) will be selected.

As a result, if your lastest build contains test errors/failures, you will need to ensure that you do not accidentally promote that build (unless you want to do so). To avoid this, simply set a more explicit sourceZipsDir such as: