Common Build Infrastructure/Publishing
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 build.eclipse.org, published over NFS to download.eclipse.org", you can use a simple Ant script, run from your crontab on build.eclipse.org.
- Copy sample promote.xml and promote.properties from org.eclipse.ve.releng or other Athana project.
- Update the promote.properties to fit your needs.
- 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 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.
# daily N builds 40 15 * * * /opt/public/common/apache-ant-1.7.1/bin/ant -f /opt/users/hudsonbuild/.hudson/jobs/cbi-ve-1.4-nightly-Ganymede/workspace/build/org.eclipse.ve.releng/promote.xml -Dpromote.properties=/opt/users/hudsonbuild/.hudson/jobs/cbi-ve-1.4-nightly-Ganymede/workspace/build/org.eclipse.ve.releng/promote-N.properties 2>/dev/null 1> ~/promo_logs/cbi-ve-1.4-nightly-Ganymede-promo.txt
# weekly I build 00 16 * * 2 /opt/public/common/apache-ant-1.7.1/bin/ant -f /opt/users/hudsonbuild/.hudson/jobs/cbi-ve-1.4-integration-Ganymede/workspace/build/org.eclipse.ve.releng/promote.xml -Dpromote.properties=/opt/users/hudsonbuild/.hudson/jobs/cbi-ve-1.4-integration-Ganymede/workspace/build/org.eclipse.ve.releng/promote-I.properties 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:
(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 your version of Hudson, a better way is needed. 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):
/opt/users/hudsonbuild/.hudson/jobs/HUDSON_JOB_NAME/N201001031122 /opt/users/hudsonbuild/.hudson/jobs/HUDSON_JOB_NAME/2010-01-03_11-22-33/archive/build/N201001031122 /opt/users/hudsonbuild/.hudson/jobs/HUDSON_JOB_NAME/workspace/build/N201001031122
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 is a failure, you will need to ensure that you do not accidentally promote that build if you do not want to. To avoid this, simply set a more explicit
sourceZipsDir such as:
If you always want to publish your latest build, use:
- bug 273302, bug 270849, bug 284593, bug 302170
- per-project promote.xml wrapper
- common promote.xml