Difference between revisions of "Common Build Infrastructure/Defining Binary Dependencies"
|Line 27:||Line 27:|
:''In the above example, Eclipse 3.5+ is required to install both IUs in a single operation from a remote update site zip.''
:''In the above example, Eclipse 3.5+ is required to install both IUs in a single operation from a remote update site zip .''
:''In the above example, Eclipse 3.4+ is required to install each IUs in separate operations from a local update site zip.''
:''In the above example, Eclipse 3.4+ is required to install each IUs in separate operations from a local update site zip .''
Revision as of 00:53, 27 November 2009
There are multiple ways to define your dependencies when doing an Athena build. Below are examples which can be used in your build.properties file.
Note that instead of http:// or ftp:// paths, you can also specify /path/to/some.zip. Once a zip has been fetched from remote, it will be cached in your
downloadsDir for reuse - but you need not reference it by a local path since the build system will check the
downloadsDir for a matching zip before attempting to re-download it from remote.
downloadsDir will be
c:\tmp\build\downloads\ on Windows); to set a different location, use the
downloadsDir property in your build.properties to point to an alternate path.
SDK or Runtime Zips
By default, everything listed in
dependencyURLs will be installed automatically. Should you want to override this behaviour, you can define your own buildExtra.xml or testExtra.xml and inject custom steps for unpacking dependencyURLs. Zips containing "master" or "update" in their name will be treated as update sites; all others will be unpacked into
# CDT master zip is an update site zip w/ p2 metadata and site.xml dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/eclipse-SDK-3.4.2-linux-gtk-ppc.tar.gz,\ http://download.eclipse.org/tools/cdt/releases/ganymede/dist/cdt-master-5.0.2.zip,\ http://download.eclipse.org/birt/downloads/drops/R-R1-2_3_2_1-200904141342/birt-report-framework-2_3_2_1.zip,\ http://download.eclipse.org/modeling/emf/emf/downloads/drops/2.4.2/R200902171115/emf-runtime-2.4.2.zip
In the past, you needed to specify your platform's SDK in order to build. Now, you can provision the entire build and test runtime environment using p2 repos so that your build can be run on multiple platforms without having to change the input dependencies. You will still have to set a different path for JAVA_HOME and other filesystem constants in
You can install a mix of features, plugins, and feature.groups like this:
- In the above example, Eclipse 3.5+ is required to install both IUs in a single operation from a remote update site zip using the "+" operator.
- In the above example, Eclipse 3.4+ is required to install each IUs in separate operations from a local update site zip using the "," operator.
repositoryURLs=file:/tmp/build/downloads/eclipse-Update-R-3.5.1-200909170800/ featureIDsToInstall=org.eclipse.sdk pluginIDsToInstall=org.eclipse.sdk.ide
- In the above example, Eclipse 3.4+ is required to install each IUs in separate operations from a local update site.
Eclipse 3.4 (Ganymede)
Provisioning directly from an update site may fail due to socket timeouts; however, this method can work when the network is cooperative.
dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/eclipse-SDK-3.4.2-linux-gtk.tar.gz repositoryURLs=http://download.eclipse.org/releases/ganymede/ featureIDsToInstall=org.eclipse.emf,org.eclipse.birt,org.eclipse.cdt
Or, specify multiple update sites:
dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/eclipse-SDK-3.4.2-linux-gtk.tar.gz repositoryURLs=\ http://download.eclipse.org/tools/cdt/updates/ganymede/,\ http://download.eclipse.org/modeling/emf/updates/releases/,\ http://download.eclipse.org/birt/update-site/2.3/ featureIDsToInstall=org.eclipse.emf,org.eclipse.birt,org.eclipse.cdt
Eclipse 3.5 (Galileo)
With Eclipse 3.5, you can do multiple provisioning installs in a single p2 operation. Note the use of "+" to define which feature.groups to install together. You can still use commas to define sequential operations.
dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-linux-gtk.tar.gz repositoryURLs=http://download.eclipse.org/releases/galileo featureIDsToInstall=org.eclipse.emf+org.eclipse.birt+org.eclipse.cdt
You can also install plugins from, for example, an Orbit update site (MUST BE A p2 REPO, not simply a "Classic" update site):
dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-linux-gtk.tar.gz repositoryURLs=http://download.eclipse.org/tools/orbit/downloads/drops/R20090825191606/updateSite pluginIDsToInstall=org.apache.xml.resolver+javax.xml+org.apache.xml.serializer+org.apache.xerces+org.apache.xalan
Remote Zipped Site
As noted above, you can use update site zips as
dependencyURLs. However, it's probably better to set them as
repositoryURLs since that is what they are. Using the
http://www.eclipse.org/downloads/download.php?r=1&file= prefix will fetch the specified zip from the mirror deemed to be closest to your IP address, unpack it, and if necessary, generate p2 metadata from the included site.xml file.
dependencyURLs=\ http://download.eclipse.org/eclipse/downloads/drops/R-3.4.2-200902111700/eclipse-SDK-3.4.2-linux-gtk.tar.gz repositoryURLs=\ http://www.eclipse.org/downloads/download.php?r=1&file=/modeling/emf/emf/downloads/drops/2.4.2/R200902171115/emf-sdo-xsd-Update-2.4.2.zip,\ http://www.eclipse.org/downloads/download.php?r=1&file=/tools/gef/downloads/drops/3.4.2/R200902171642/GEF-Update-3.4.2.zip featureIDsToInstall=org.eclipse.emf,org.eclipse.gef
In most builds, the resulting zips contain the timestamp of the build. As such, each build will produce a uniquely named set of zips. This is perfect for ensuring you know what's in the zip, and how old it is, but not as useful for creating cascades of builds which depend on the output of others.
So, to solve this problem, you can build and consume snapshot zips. These are identical to the output of a normal build except that they are named more generically so that as they are replaced hourly or daily, their NAME does not change.
To provide others with SNAPSHOT builds (usually nightlies), set the following property when running your Athena build (via Hudson or commandline):
export SNAPSHOT="true" . /opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/run.sh
To consume others' SNAPSHOT builds, explore their Hudson jobs to find their "Last Successful Build" then "Build Artifacts". Browse their workspace for a generically named zip such as this one:
Then, add this zip to your
build.properties file via the
repositoryURLs as appropriate, depending on whether the snapshot zip contains an SDK/runtime or p2 repository (update site).
- buildAllHelper.xml - Ant tasks used to handle p2 repos, update sites, and SDK zips
- getDependencies.xml - Ant tasks to automate downloading and unpacking zips
- See also bug 273518