Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Common Build Infrastructure/Publishing

Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.

OK, so you've built your SDK or runtime zip, your examples, your docs, your tests, and a p2 repo / update site. Great. How do you get those bits out to the world?

Well, for the simple case of "built on, published over NFS to", you can use a simple Ant script, run from your crontab on

  1. Copy sample promote.xml and from or other Athana project.
  2. Update the to fit your needs.
  3. Add entry in your crontab that will invoke the promote.xml Ant script.

Example: VE Nightly and Integration Builds


Say you want to run Nightlies every day, and a single Integration build once a week. First, set up two jobs in Hudson:


(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 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.

# daily N builds
40 15 * * *  JAVA_HOME=/shared/common/ibm-java-x86_64-60 ANT_HOME=/shared/common/apache-ant-1.7.1/ ant -f
      2>/dev/null 1> ~/promo_logs/cbi-ve-1.4-nightly-Ganymede-promo.txt
# weekly I build
00 16 * * 2 JAVA_HOME=/shared/common/ibm-java-x86_64-60 ANT_HOME=/shared/common/apache-ant-1.7.1/ ant -f
      2>/dev/null 1> ~/promo_logs/cbi-ve-1.4-integration-Ganymede-promo.txt

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 building locally, or


if building on, where HUDSON_JOB_NAME = cbi-ve-1.5-Helios, cbi-tmf-xtext-0.7, etc.

However, since lastSuccessfulBuild or lastStableBuild symlinks may not work with the latest version of Hudson, a better way is needed (bug 302170). For a sourceZipsDir such as:


Athena will attempt to find your build dir based on three well-known patterns, for all buildTypes specified (eg., N, I, M, S and/or R):


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:


If you always want to publish your latest build, use:



Copyright © Eclipse Foundation, Inc. All Rights Reserved.