Community
Participate
Working Groups
Need a script/process of doing/managing automated builds.
I started with a simple PDE build setup for the UDC feature on build.eclipse.org. The first results will be available in CVS .../releng/org.eclipse.epp.usagedata.releng soon. Some open issues: * version numbers * test integration * when do we start a build (AFAIK there is no common build infrastructure or continous integration available at eclipse.org, e.g. something like luntbuild, Hudson, CruiseControl, ...) I still have to work on it, but I wanted to avoid that we both start working on the same issue.
* build starts every night 10.15pm on build.eclipse.org * it writes output update site to a 'test' directory on the download server http://download.eclipse.org/technology/epp/updates/testing/
* plugins and feature org.eclipse.epp.usagedata.feature are signed now by default to disable signing, modify the start.sh script * jars are now compressed with pack200 * test feature org.eclipse.epp.usagedata.tests.feature is build, but there is no automated test-setup/run (yet) * digest is not yet available
I am taking ownership of this to update the scripts.
I have committed changes that allow the build to be run on either the server or on my laptop. Currently the start.sh script supports an optional parameter for the buildType (I, N, R, ...). If not specified, 'N' is assumed. I am currently sending the output of the build to a different directory based on the build type. Need to think about this some more. At least should consider directories named "releases", "nightly" instead of "R", "N". Should be easy enough to script. The proper paths of the launcher JAR and PDE Build plug-in directors are dynamically sorted out. I've added generation of p2 metadata to the end. I couldn't quite sort out how to make PDE build do it, so I'm currently using the EclipseGenerator for this. Build will now only attempt to sign JARs if the signer is available. Gracefully ignores signing if it is not. It currently pulls JARs from Orbit and includes them in the generated update site. I want to instead automate the process of creating the build base; I believe that I can do this with a little help from the p2 director to install the required Orbit bundles. The end result will be an update site that excludes these bundles. We're also currently building from HEAD. Probably should be building from a tag. I also intend to further generalize the build script to run on any system.
Created attachment 131969 [details] mylyn/context/zip
*** This bug has been marked as a duplicate of bug 301767 ***
