Common Build Infrastructure/Migration to Ant

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

There are two steps to migrate from bash to ant: project configuration and job configuration. In both cases the net effect is simplification and better ease of use.

Project Configuration

1. Update your build.xml to the latest template version

2. Replace custom values in build.properties with generic ones which will work in both Eclipse or in Jenkins

Project Configuration

Old Configuration	New Configuration
Sample build.properties, server version (diff) Sample build.properties, windows version	Sample build.properties, GEF example (diff) Sample build.properties, template version (diff)
Sample build.xml, GEF example (diff) Sample build.xml, template version (diff)	Sample build.xml, GEF example (diff) Sample build.xml, template version (diff)
Before, you needed one configuration file per platform. JAVA_HOME=/opt/public/common/ibm-java2-ppc-50 JAVA14_HOME=/opt/public/common/ibm-java2-ppc-50 JAVA50_HOME=/opt/public/common/ibm-java2-ppc-50 JAVA60_HOME=/opt/public/common/ibm-java2-ppc-50	Now you can still hardcode values, or use the defaults from Eclipse or Jenkins. JAVA14_HOME=${JAVA_HOME} JAVA50_HOME=${JAVA_HOME} JAVA60_HOME=${JAVA_HOME}
Before, you needed one configuration file per platform because you depend on a given Eclipse SDK. dependencyURLs=http://.../eclipse-SDK-3.5.1-linux-gtk-ppc.tar.gz or dependencyURLs=http://.../eclipse-SDK-3.5.1-win32.zip	Now, depend on an update site and properties will work on all supported platforms. repositoryURLs=http://.../eclipse-Update-3.5.2-201002111343.zip IUsToInstall=org.eclipse.sdk.feature.group or repositoryURLs=http://download.eclipse.org/releases/helios/ IUsToInstall=org.eclipse.sdk.feature.group
Before, because you needed have one properties file per platform, you could set these in build.properties: localSourceCheckoutDir=C:/workspace/org.eclipse.gef.tree localSourceCheckoutDirExcludes=**/archive/** # For windows, must be explicit about paths using correct # slashes (/); dirs with spaces should be avoided relengBuilderDir=C:/workspace/org.eclipse.gef.releng relengBaseBuilderDir=C:/workspace/org.eclipse.releng.basebuilder relengCommonBuilderDir=C:/workspace/org.eclipse.dash.common.releng writableBuildRoot=C:/tmp/build	Remove the values set in build.properties, as they are now computed and should not be needed. Now, set this in an optional build.local.xml file so it won't conflict with the server's "build from maps" version. This additional step is only needed if building from local sources; otherwise build.xml will work without modification on local or in Jenkins! <property name="localSourceCheckoutDir" value="${basedir}/.." /> <property name="relengBuilderDir" value="${basedir}" /> or <property name="localSourceCheckoutDir" value="/path/to/dir/A /> <property name="relengBuilderDir" value="/path/to/dir/B" />

Jenkins Job Configuration

Migration To Ant Job

Old Configuration	New Configuration
Sample Bash job: config.xml	Sample Ant job: config.xml
Under Build click Add build step > Execute shell. Enter this configuration: export PROJRELENGROOT='-projRelengRoot :pserver:anonymous@dev.eclipse.org:/cvsroot/dsdp' export PROJRELENGPATH='-projRelengPath org.eclipse.tm.rse/releng/org.eclipse.tm.releng' #export SNAPSHOT="true" # run the build . /opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/run.sh	Under Build click Add build step > Invoke Ant. Set targets = run or leave blank to run default. Click Advanced button Define path to your build.xml script relative to job's workspace, eg. org.eclipse.tm.rse/releng/org.eclipse.tm.releng/build.xml. Define these properties: relengBaseBuilderDir=/opt/public/cbi/build/org.eclipse.releng.basebuilder relengCommonBuilderDir=/opt/public/cbi/build/org.eclipse.dash.common.releng #SNAPSHOT="true"
In your build.properties file, use build.steps=test for Linux, or build.steps=test for Windows/Mac. Curse when tests fail unexpectedly due to X server DISPLAY port collisions (two or more builds using the same DISPLAY).	Under Build Environment, enable option Run Xvnc during build. Use build.steps=testLocal for all platforms Rejoice when tests pass w/o DISPLAY port conflict!