Skip to main content
Jump to: navigation, search


Note: Most of the data in this FAQ is obsolete, but it may still contain some interesting tid-bits.

Eclipse Platform Release Engineering FAQ


Basic overview of Platform releng tasks and troubleshooting tips

Platform releng basics

What hardware comprises the platform-releng build infrastructure?

The eclipse platform build infrastructure consists of

  1. junit test machines,
    1. ejwin1 (winxp with 1.5 vm) 5 on KVM on table
    2. ejwin2 (winxp with 1.6 vm 6 on KBM on table
    3. lb6mac (macosx Leopard) mac on table on LHS of lab
    4. ejlnx1 (RHEL 5.3 with 1.5 vm) 5 on large KVM in rack
    5. ejlnx2 (RHEL 5.3 with 1.6 vm) E on large KVM in rack
  2. performance machines
    1. epwin2 (winxp with 1.5 vm) G on large KVM in rack
    2. epwin3 (winxp with 1.6 vm) 7 on large KVM in rack
    3. eplnx1 (SLES 10 with 1.6 vm) H on large KVM in rack
    4. eplnx2 (RHEL 5.2 with 1.6 vm) F on large KVM in rack
  3. Other
    1. minsky (database server with apache derby installed to store performance test results), (cvs test server)
    2. eclipsebuildserv (build machine) Linux machine on far back table of the room

The linux machines should be logged in as kmoir. The windows machines should be logged in as the default user. If the build machines don't have the correct user logged in, the ui tests will fail. All the test machines have 2 x 3.00Ghz processors and 3GB of memory.

Is the Eclipse platform build process completely automated?

Yes, the Eclipse build process starts with a cron job on our main build machine that initiates a shell script that checks out the builder projects.

  • org.eclipse.releng.eclipsebuilder -> scripts to build each type of drop
  • org.eclipse.releng.basebuilder -> a subset of eclipse plugins required to run the build.
  • we also use several small cvs projects on an internal server that store login credentials, publishing information and jdks

Fetch and build scripts are generated automatically by the bundle in org.eclipse.releng.basebuilder. Fetch scripts specify the version of code to retrieve from the repository. Build scripts are also generated automatically to compile all java code, determine compile order and manage dependencies. We create a master feature of all the non-test bundles and features used in the build. This feature is signed and packed, and the we create a p2 repo from the packed master feature. Metadata for the products is published to the repository. We then use the director application to provision the contents of the SDKs etc to different directories and then zip or tar them up. We also use custom build scripts that you can see in org.eclipse.releng.eclipsebuilder. After the SDKs are built, the automated junit and performance testing begins. Tests occur over ssh for Linux machines, and rsh for Windows machines. Each component team contributes their own tests. Once the tests are completed,the results are copied back to the build machine. Also, the images for the performance tests are generated.

What's the difference between an integration and nightly build?

With integration builds, we specify a version of the plug-in to retrieve in the map files. (org.eclipse.releng/maps). With nightly builds, we retrieve the plug-ins specified in the map files from the HEAD stream. The types of builds we run are described here

How do I use the releng plugin?

The RelEng Plug-in repository is included in the Eclipse builds and is available at the bottom of the download page. You can install the new software from the downloaded repository or simply unzip the the 'features' and 'plugins' folder into the 'dropins' folder of your Eclipse install.

This plug-in provides the following features that will help with the Eclipse development process:

  • Fix Copyright to the Resource Perspective Projects context menu. Select one or more projects in the Resource Perspective. This action will sanity check the copyright notices in all the *.java and *.properties files. Copyrights will be updated automatically where the tool deems appropriate. A copyright.log file will be written to the workspace directory noting odd conflicts that need to be looked at.
  • Copyright Tool preference page.
  • POM Version Tool preference page. The POM Version tool will compare the artifact version in a pom.xml file at the root of the project to the plug-in version in the manifest. If the two versions do not match, a problem marker will be created. The option is set to 'Ignore' by default. Eclipse bundle developers should set this to 'Error'.

The following functionality is no longer used for Eclipse build inputs that moved to Git/CBI/Maven:

  • Release to the Team menu. This action will tag selected projects with the specified version and update the appropriate loaded *.map files with the version. The user must have the *.map files loaded in their workspace and the use must commit the map file changes to the repository when done.
  • Load Map Projects to the Team menu. Select one or more *.map file and this action will load the projects listed in the *.map file into your workspace. Naturally the versions specified in the *.map file will be loaded.
  • Tag Map Projects to the Team menu. Select one or more *Map files and this action will tag the projects listed in the *Map files with a tag you specify.
  • Compared with Released to the Compare menu. Compare the selected projects with the versions referenced in the currently loaded map files.
  • Replace with Released to the Replace menu. Replace the selected projects with the versions referenced in the currently loaded map files.

How do I run a build using the scripts in org.eclipse.releng.eclipsebuilder?

This document provides an overview of how to build eclipse components using the releng scripts. However, it is really out of date. Your best bet is to use the source build to recompile the SDK.

What is the latest version of org.eclipse.releng.basebuilder?

See this document which describes correct tag of org.eclipse.releng.basebuilder for use in your builds.

How do I automate my builds with PDE Build?

See the PDE/Build wiki page.

How do I contribute a JUnit Plug-in Test to the build?

  1. The tests need to be contributed as one or more plugins that use the org.eclipse.test automated testing framework. JUnit tests can also be written as performance tests. Click here for the latest instructions.
  2. Open bug for for PMC approval for new plug-in projects on CC webmaster on the bug once the plug-ins are created. Or you may want to include the new plug-ins under an existing project and in this case, the webmasters don't need to get involved.
  3. Add the new test plugin to the org.eclipse.releng project in the appropriate map file for your component.
  4. Install the org.eclipse.releng tools plug-in, and use the "Release" action in the context menu of the test plug-in project to update and commit map file.
  5. Open a bug against platform releng to add the plugins to the build process. Include the following information:
  • the plug-in id(s)
  • the plug-ins that contain a test.xml
  • update the to include the test.xml
  • additional steps to setup the tests outside of installing the test plugins and framework in an Eclipse SDK

The Eclipse release engineering team will update the appropriate feature and scripts to build and run the new tests.

How do I contribute an example plug-in to the build?

Once you have your plug-in ready and available in CVS, install the plug-in, and use the "Release" action in the context menu of the test plug-in project to update and commit the map file.

Next, open a bug against platform releng with the plug-in's id.

The Eclipse release engineering team will update the org.eclipse.sdk.examples-feature to include the new tests. They will also update org.eclipse.releng.eclipsebuilder/all/publishing/templateFiles/testManifest.xml to indicate the zip that should get a red X if there are compile errors associated with that plug-in on the build page.

Testing the 4.2 build on

Just documenting the current issues here (March 21, 2012)

The builder to build the 4.2 primary build is the R4_2_primary branch of org.eclipse.releng.basebuilder and org.eclipse.releng.eclipsebuilder

The branch of the map files with the bundles to build are R4_HEAD. There are a few weeks out of date. This is just for testing.

e4Build@build:/shared/eclipse/e4> pwd /shared/eclipse/e4 e4Build@build:/shared/eclipse/e4> ls

Is the script that invokes the build. It needs to be refactored a bit. Also, the bits that tag the repos have been commented out because I don't want to pollute the the 4.2 maps until we have the other issues worked out.

In our regular 3.8 stream builds we have scripts in the bootstrap script that update the tags in the map files repo. The eclipse.platform.releng.maps\org.eclipse.releng\tagging\repositories.txt file lists the appropriate branches to look for each repo.

These scripts update the maps with a timestamp in the tags field of the appropriate project. This is disabled for now for testing purposes.

Anyways, the issues and notes 1) The current 4.2 stream org.eclipse.platform.doc.isv bundle copies over some content from the 3.x stream of this same bundle. This needs to be deleted once we move to 4.2 build primary 2) update.core has been added added to sdk.tests feature because some of the tests still depend on it. 3) update.tests.core has been removed for org.eclipse.sdk.tests feature because these tests aren't relevant anymore 4) The 4.2 versions sdk and platform features have parts commented in their that are commented out. These need to be uncommented and released when we move to the 4.2 build primary so the appropriate source bundles are produced. I've temporarily uncommented them and tagged them for the R4_HEAD version of org.eclipse.releng. 5) The e4 build part doesn't run yet, I just build the e4 bundles needed for the platform. 6) Need to add the 4.2 stream tests to the sdk.tests feature and run them, right now it just includes the 3.8 stream tests. 7) The test results page generation also needs to be updated to include all the tests. 8)I use a hudson token to invoke the tests via JSON. This needs to be stored somewhere secure. Right now, I just add it to the command.txt when hacking the build. 9) The build isn't copied to the correct location, signed or mirrored into the correct repo because it's just a test build.

I would like to recompile eclipse on a platform that is not currently supported. What is the best approach to this? How can I ensure that the community can use my work?

The best approach is use the source build drop and modify the scripts to support that you are interested in. Then open a bug with product Platform and component Releng attaching the patches to the scripts that were required to build the new drop. If you are interested in contributing a port to eclipse, here is the procedure.

How does the platform team sign their builds?

See Platform-releng-signedbuild

How long does the build take to complete?

It takes three hours and 20 minutes for all the drops to be produced. JUnit (eight hours) and performance tests (twelve hours) run in parallel after the windows, mac, linux and sdk tests drops have been built. It takes another two hours for the performance results to be generated.

When is the next build?

Please refer to the build schedule.

David Williams and John Arthorne have rights to update this calendar.

When is the next milestone?

Please refer to the Eclipse Platform Project Plan.

I noticed that you promoted an integration build to a milestone build. The integration build had test failures but the milestone builds doesn't show any. Why is this?

See bug 134413.

We have a number of tests that intermittently fail. The reasons are

  • issues with the tests themselves
  • tests subject to timing issues
  • tests that fail intermittently due to various conditions

The component teams are always trying to fix their tests but unfortunately they are still some issues. When we promote a build to a milestone, we rerun the tests that failed. Many pass on the second time because the tests initially failed due to a timing issue or intermittent condition. Or a team will have a broken test that doesn't warrant a rebuild for a milestone. In that case, the releng team sprinkles pixie dust over the build page to erase the red Xes, but leaves the appropriate build failures intact.

Scripts to promote a 3.x stream build

  • Disable rsync
  • cd /home/users/releng/buildTools/extraTools on eclipsebuildserv
  • See parameters... ./builds/tools/jdk/linux/jdk1.4/bin/java -cp promote33.jar PromoteBuild.PromoteBuild
    • Usage: PromoteBuild <oldBuildDirectory> <newTypePrefix> <newName>
  • Promote eclipse milestone build
    • ./builds/tools/jdk/linux/jdk1.4/bin/java -cp promote33.jar PromoteBuild.PromoteBuild /builds/transfer/files/master/downloads/drops/I20080925-0800 S 3.5M4
  • Promote equinox build
    • ./builds/tools/jdk/linux/jdk1.4/bin/java -cp promote33.jar PromoteBuild.PromoteBuild /builds/transfer/files/master/equinox/drops/I20080925-0800 S 3.4M4
  • Extract new and noteworthy zip to S-... directory on eclipsebuildserv. Update index.php to include New and Noteworthy link.
  • Enable rsync, wait until build is synched to (Takes 1-2 hours)
  • Copy child repo to appropriate milestone or release repo. Update compositeArtifacts.jar and compositeContent.jar to include properties to point to the child repo. Update the child repo's artifacts.jar to include the correct link the the p2.mirrorsURL property.
  • Send out message to eclipse-dev,,
  • Enjoy post-milestone chocolate.

Scripts to promote a 4.x stream build

ssh to as pwebster

./ ${buildId} ${milestonename}

Example ./ I20110916-1615 M2

update the index.html to reflect the new build


How to hide a build to allow it to sync to the mirrors

kmoir@build:/home/data/httpd/> pwd


php eclipse3x.php > eclipse3x.html


kmoir@build:/home/data/httpd/> vi createIndex4x.php kmoir@build:/home/data/httpd/> vi index.html

to point to eclipse3x.html instead of eclipse3x.php

revert the changes when the build is ready to release

I'd like to run a build with the version of the code that was used for build X? How do I know what versions of code in the repository were used?

There are several ways to approach this issue.

  • Look at the directory.txt linked from the top of every build page. The directory.txt concatenates all the map files used in a build into a single file. Please note that every nightly build runs from HEAD. Therefore it is impossible to replicate a nightly build.
  • In addition, with every maintenance and integration build, the org.eclipse.releng project, which contains the map files for each project, is tagged with a version corresponding to that build. For instance, the version I20051018-0932 corresponds to the integration build of the same name. Please note that the builder projects, (org.eclipse.releng.eclipsebuilder and org.eclipse.releng.basebuilder) are also tagged during an integration build with the corresponding build name, but are not reflected in the directory.txt because they are not included in the eclipse distribution itself.
  • Finally, after each release the releng team tags all projects from the map files used in the release. So, all the projects used to construct version 3.1.1 are tagged R_3_1_1.

I'm looking for an older build but can't find them on the download page?

Check out archive site the for vintage builds.

How do I run a test build on the hudson install at ?

Login to this web page with your committer id and password.

On the left hand side, select "Build Now". Your test nightly build will be available in about three hours, depending on the load average on the eclipse Hudson slaves. This build isn't signed or packed to save time. Once the build is finished, select "Build Artifacts" to to look at the SDKs etc (/builds/transfer/files/bogus/download/drops/${buildId}) or p2 repo (/builds/transfer/files/repo/).

This build will also run tests on three platforms (Windows 7, Linux, and Mac OS X10.6). These take six to eight hours to complete. There are still a few remaining issues respect to running several test suites on a some platforms. For more details, see bug

How do I run the JUnit tests used in the build?

With every build, there is a eclipse-Automated-Tests-${buildId}.zip file. You can follow the instructions associated with this zip to run the JUnit tests on the platform of your choice.

How do you run the tests on the Windows machine via rsh

To run the windows tests from the build machine,

rsh ejwin2 start /min /wait c:\\buildtest\\N20081120-2000\\eclipse-testing\\testAll.bat c:\\buildtest\\N20081120-2000\\eclipse-testing winxplog.txt

Where do you find the Java SDK for the Mac (This is required to run the JDT debug JUnit tests)

The default Mac install only includes a JRE, not a JDK. The JDK is listed under Apple Connect under J2SE 5.0 Release 5 Developer Documentation. Once the .dmg is installed, you should see a src.jar under /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home


How do I set up a test cvs server to run the cvs tests portion of the JUnit tests?

This document outlines the steps required to setup a test CVS repository on Linux.

How do I set up performance tests?

Refer to the performance tests how-to or the even better Performance First talk at Eclipse Con 2007.

Baseline tests are run from a branch of the builder.

  • 3.8 builds are compared against 3.4 baselines in the perf_37x branch of org.eclipse.releng
  • 3.7 builds are compared against 3.4 baselines in the perf_36x branch of org.eclipse.releng
  • 3.6 builds are compared against 3.4 baselines in the perf_35x branch of org.eclipse.releng
  • 3.5 builds are compared against 3.4 baselines in the perf_34x branch of org.eclipse.releng
  • 3.4 builds are compared against 3.3 baselines in the perf_33x branch of org.eclipse.releng
  • 3.3 builds are compared against 3.2 baselines in the perf_32x branch of org.eclipse.releng

How do I find data for old performance results on existing build page?

Refer to the "Raw data and Stats" link for a specific test.

For instance for results, click here

Then look at the jdt ui tests.

Then click on a specific test.

Then click "Raw data and Stats".

You will see the data for previous builds.

How do I run the performance tests from the zips provided on the download page?

See here.

Process to implement a new baseline

Implement new performance baseline after a release.

How to regenerate performance results from build artifacts

This assumes that the artifacts used to run the build and the resulting build directory itself still exist on the build machine.

  • cd to build directory on build machine
  • cd org.eclipse.releng.eclipsebuilder
  • apply patch to builder in bug [256297]
  • rerun generation on hacked builder
  • on build machine
    • at now
    • cd /builds/${buildId}/org.eclipse.releng.eclipsebuilder; sh command.txt
    • ctrl d

The process needs to be executed using at or cron if you are logged in remotely because the swt libraries are needed to run the generation. If you run the process while logged in remotely via ssh, the process will fail with "No more handles". The output logs for this process are in the posting directory under buildlogs/perfgen*.txt.

The user that's running the tests on the build machine needs run "xhost +" in a terminal on the build machine.

How to regenerate performance results from build artifacts

This assumes that the artifacts used to run the build and the resulting build directory itself still exist on the build machine.

  • cd to build directory on build machine
  • cd org.eclipse.releng.eclipsebuilder
  • apply patch to builder in bug [256297]
  • rerun generation on hacked builder
  • on build machine
    • at now
    • cd /builds/${buildId}/org.eclipse.releng.eclipsebuilder; sh command.txt
    • ctrl d

The process needs to be executed using at or cron if you are logged in remotely because the swt libraries are needed to run the generation. If you run the process while logged in remotely via ssh, the process will fail with "No more handles". The output logs for this process are in the posting directory under buildlogs/perfgen*.txt.

The user that's running the tests on the build machine needs run "xhost +" in a terminal on the build machine.

How performance tests are invoked in the build

Performance tests run if the -skipTest or -skipPerf parameters isn't passed to the build when running it. Both JUnit and performance tests are invoked in the build by the testAll target in the org.eclipse.releng.eclipsebuilder/buildAll.xml

<target name="testAll" unless="skip.tests">
		<waitfor maxwait="4" maxwaitunit="hour" checkevery="1" checkeveryunit="minute">
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-Automated-Tests-${buildId}.zip.md5" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-SDK-${buildId}" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-SDK-${buildId}-linux-gtk.tar.gz.md5" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-SDK-${buildId}-macosx-cocoa.tar.gz.md5" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-${buildId}" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-platform-${buildId}" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-platform-${buildId}-linux-gtk.tar.gz.md5" />
				<available file="${postingDirectory}/${buildLabel}/checksum/eclipse-platform-${buildId}-macosx-cocoa.tar.gz.md5" />

		<property name="" value="${base.builder}/../eclipseInternalBuildTools/" />
		<antcall target="" />

		<!--replace buildid in for JVM location settings-->
		<replace dir="${}/sdk.tests/testConfigs" token="@buildid@" value="${buildId}" includes="**/" />

		<antcall target="addnoperfmarker" />

			<antcall target="test-JUnit" />
			<antcall target="test-performance" />

The test-performance target in the buildAll.xml looks like this

	<target name="test-performance" unless="skip.performance.tests">

		<echo message="Starting performance tests." />
		<property name="dropLocation" value="${postingDirectory}" />
		<ant antfile="testAll.xml" dir="${}/sdk.tests/testConfigs" target="performanceTests" />
		<antcall target="generatePerformanceResults" />

This calls the testAll.xml in org.eclipse.releng.eclipsebuilder/sdk.tests/testConfigs

<target name="performanceTests">

		<condition property="internalPlugins" value="../../../eclipsePerformanceBuildTools/plugins">
			<isset property="performance.base" />

		<property name="testResults" value="${postingDirectory}/${buildLabel}/performance" />
		<mkdir dir="${testResults}" />

			<antcall target="test">
				<param name="tester" value="${basedir}/win32xp-perf" />
				<param name="cfgKey" value="win32xp-perf" />
				<param name="markerName" value="eclipse-win32xp-perf-${buildId}" />
			<antcall target="test">
				<param name="tester" value="${basedir}/win32xp2-perf" />
				<param name="cfgKey" value="win32xp2-perf" />
				<param name="markerName" value="eclipse-win32xp2-perf-${buildId}" />
			<antcall target="test">
				<param name="tester" value="${basedir}/rhelws5-perf" />
				<param name="sleep" value="120" />
				<param name="cfgKey" value="rhelws5-perf" />
				<param name="markerName" value="eclipse-rhelws5-perf-${buildId}" />
			<antcall target="test">
				<param name="tester" value="${basedir}/sled10-perf" />
				<param name="sleep" value="300" />
				<param name="cfgKey" value="sled10-perf" />
				<param name="markerName" value="eclipse-sled10-perf-${buildId}" />

This invokes the tests in parallel on the performance test machines. In this case, there is a machine.cfg file in the same directory as the above file that maps the "cfgKey" value written above to the hostname of the machine. The tests are invoked on the windows machines via rsh and on the linux machines via ssh.

#Windows XP

#RedHat Enterprise Linux WS 5

#sled 10 

This invokes all the tests in the org.eclipse.releng.eclipsebuilder\eclipse\buildConfigs\sdk.tests\testScripts\test.xml on each machine. If the test bundle has a performance target in the test.xml, the performance tests for that machine will run. The test scripts use the values in the (for example when running on window xp) org.eclipse.releng.eclipsebuilder\eclipse\buildConfigs\sdk.tests\testConfigs\win32xp2-perf\ which specifies the database to write to as well as the port, and url of that database.

When the performances tests complete, the results are generated.

<target name="generatePerformanceResults">
		<mkdir dir="${buildDirectory}/${buildLabel}/performance" />
		<mkdir dir="${postingDirectory}/${buildLabel}/performance" />
		<taskdef name="performanceResults" classname="org.eclipse.releng.performance.PerformanceResultHtmlGenerator" />
		<condition property="configArgs" value="-ws gtk -arch ppc">
			<equals arg1="${os.arch}" arg2="ppc64" />
		<condition property="configArgs" value="-ws gtk -arch x86">
			<equals arg1="${os.arch}" arg2="i386" />
		<property name="configArgs" value="" />

		<java jar="${basedir}/../org.eclipse.releng.basebuilder/plugins/org.eclipse.equinox.launcher.jar" fork="true" maxmemory="512m" error="${buildlogs}/perfgenerror.txt" output="${buildlogs}/perfgenoutput.txt">
			<arg line="${configArgs} -consolelog -nosplash -data ${buildDirectory}/perf-workspace -application org.eclipse.test.performance.ui.resultGenerator
						-current ${buildId}
						-jvm ${eclipse.perf.jvm}
						-output ${postingDirectory}/${buildLabel}/performance/
						-config eplnx1,eplnx2,epwin2,epwin3
			            -dataDir ${postingDirectory}/../../data/v38 ${eclipse.perf.config.descriptors}
						-scenario.pattern org.eclipse.%.test%" />
			<!-- baselines arguments are no longer necessary since bug has been fixed...
						-baseline ${eclipse.perf.ref}
						-baseline.prefix R-3.4_200806172000
			<!-- add this argument to list above when there are milestone builds to highlight 
			-highlight.latest 3.3M1_
			<env key="LD_LIBRARY_PATH" value="${basedir}/../org.eclipse.releng.basebuilder" />
			<sysproperty key="eclipse.perf.dbloc" value="${dbloc}" />

Two important things about generating performance results:

  1. xhost+ needs to be enabled in a terminal of the user generating the performance results
  2. The derby database needs to be running on port 1528 (There is an init script for that)
  3. X has to be open on the machine generating the results or you'll get the "SWT - no more handles error"

Why should I package plugins and features as jars?

See the Running Eclipse from JARs document from the Core team.

Why should I use qualifiers?

See the Versioning Guidelines

How do I incorporate qualifiers into the build process?

Update your plug-ins and features to use qualifiers as described in the previous FAQ entry.

Additional steps that the platform releng team uses to incorporate qualifiers into the build process.

For nightly builds, we set the qualifier to the buildId. For integration builds, pde build sets it to the tag in the map file for plugins, and generates feature qualifiers.

In our from org.eclipse.releng.eclipsebuilder/eclipse/buildAll.xml, forceContextQualifier is set to the buildId if is a nightly build

<condition property="forceContextQualifier" value="${buildId}">
    <equals arg1="${buildType}" arg2="N" />

Also, in the file which kicks off our build, we specify -DgenerateFeatureVersionSuffix=true

    -buildfile buildAll.xml

How can I run the update manager from a command line to mirror a remote site?

Refer to running update manager from command line in Eclipse Help for the latest information. It copies the appropriate versions of features and associated plugins you specify and generates the site.xml. For instance, if you wanted to create an update site for the platform feature.

I have questions about PDEBuild - where should I go for answers?

Consult the PDE Build faq or ask on the org.eclipse.platform newsgroup.

Debugging pde build with missing dependancies

Breakpoint in BuildTimeSite class, in missingPlugins method, set breakpoint In display view, state.getState().getResolverErrors(state.getBundle("org.eclipse.ui.workbench", null, false)) print the errors for the bundle in question.

I'd like to incoporate source bundles in my build, how do I do it?

See Individual Source Bundles

Are there RSS feeds for builds?

Yes, for I-Builds only. They are available here.

If I add a new plugin to a build, how do I ensure that javadoc will be included in the build.

See the adding javadoc document.

Troubleshooting test failures

If tests pass in a dev workspace but fail in the automated test harness, check to make sure that your is exporting all the necessary items; check that plug-in dependencies are correct, since the test harness environment will only include depended-upon plug-ins; and check that file references do not depend on the current working directory, since that may be different in the test harness.

To debug tests in the context of the automated test harness, add the following element to the test.xml file in your plug-in's directory in the test harness.

        value="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Djava.compiler=NONE"/>


  • create a remote debugging launch target in your dev environment
  • put a breakpoint somewhere in your code
  • launch the tests from the command line, using the -noclean option to preserve the modified test.xml
  • launch the debug target

Troubleshooting tests that crash or time out, aka "(-1)DNF"

The table "Unit Test Results" on testResults.php sometimes shows "(-1)DNF" instead of (0) or the number of failing tests. This means the tests Did Not Finish, i.e., for some reason, no <test-suite-name>.xml file was produced.

Note that the absence of a DNF entry not always means that everything is alright! E.g. in bug 474161, one of the two SWT test suites was killed by a timeout, but since the other one passed, the testResults table currently doesn't show that (which needs to be fixed, see bug 210792).

To get more information about crashes and timeouts, consult the "Console Output Logs" logs.php. In the main logs (e.g. linux.gtk.x86_64_8.0_consolelog.txt), look for entries like this:

    [java] EclipseTestRunner almost reached timeout '7200000'.


    [java] Timeout: killed the sub-process

[junitreport] the file /Users/hudsonBuild/workspace/ep46I-unit-mac64/workarea/I20150805-2000/eclipse-testing/test-eclipse/ is empty.
[junitreport] This can be caused by the test JVM exiting unexpectedly

Search for keywords almost, killed, and JVM exiting unexpectedly to quickly find the relevant region in the console log.

Before the Ant task that drives the automated tests kills the test process, the EclipseTestRunner tries to produce a thread dump and take a screenshot (twice within 5 seconds). The stack traces end up in the *_consolelog.txt, and the screenshots are made available on the logs.php page, e.g.:

Screen captures for tests timing out on linux.gtk.x86_64_8.0

Also consult the "Individual * test logs" on the logs.php page (one .txt file per test suite). Stdout output goes into those files. Stderr output goes into the *_consolelog.txt.

Since Oxygen (4.7), the org.eclipse.test.performance bundle contains a class TracingSuite that can be used instead of the normal JUnit 4 Suite runner. Just define a test suite with @RunWith(TracingSuite.class), and you will get a message on System.out before each atomic test starts. The Javadoc of the class has all details.

I would like a plaform releng committer to comment on a bug assigned to another component. What mailbox do I add to the cc list in bugzilla?

Please cc the generic mail alias Please do not just cc your favourite release engineer using their individual email address. They might be on a beach somewhere enjoying a sunny vacation and therefore unable to comment.

Eclipse Release checklist

New JUnit/performance machine deployment checklist

Steps to take after OS install from IT

All platforms

  • verify hostname is set on machine
  • verify hostname is registered in DNS and both forward and reverse lookups resolve correctly
  • disable screen saver
  • disable all power management options so that the machine, disk, monitor etc is always on
  • create c:\buildtest or /buildtest directory and ensure the build user owns it and can write to it
  • install ganglia and configure to interact with appropriate eclipse build node
  • verify that the machines can access all ports required for testing, port 2401,22 to cvs test server, port 1527, 1528 to database server, and access via http to,
  • disable real time virus scanning of build directories
  • ensure that machines starts as build user automatically upon reboot


  • install rshd
    • set rshd user equivalency to build user
    • ensure rshd daemon is run in normal mode (default is hidden) and starts automatically upon startup
  • ensure cvs, zip and unzip binaries are installed and update the path environment variable to include them


  • copy ssh keys from build machine to test machines and ensure that ssh logins occur without user intervention
  • ensure that correct mozilla/xulrunner libraries are installed in the build and match those defined in the build test scripts for SWT tests
  • update /etc/hosts to include localhost
  • disable iptables in chkconfig and stop the service

Process to release builds to Simultaneous Release

  • Check out or from /cvsroot/callisto.
  • For eclipse platform, update versions in ep.b3aggrcon, for equinox equinox.b3aggrcon
  • Copy child repo from integration build site or maintenance build site into the appropriate milestone or release site. Update compositeContent.jar and compositeArtifacts.jar to reflect the new child repo.
  • Watch build message to ensure coordinated release build completes successfully.

How do I verify the signatures of packed jars on an update site?

See bug 193568 for the tool and instructions.

Where are the p2 update sites for the Eclipse Project?

See the list

How do I remove a bad build from an update site?

  • SSH to
  • cd /home/data/httpd/
  • emacs compositeContent.jar
  • press Enter to edit the compositeContent.xml
  • remove the bad build from the list (C-k deletes a line)
    • don't bother to fix p2 file format garbage like the size='7' attribute or the p2.timestamp
  • exit and save file (C-x C-c, y)
  • do the same with compositeArtifacts.jar

When is this used? Bad N-builds can e.g. kill Gerrit automated builds that use the build-individual-bundles profile and take the rest form an update site.

How do I use the p2 zipped repos on the build page to provision my install or a pde target?

Where can I download foundation libraries?

Anyone can get access to the foundation 1.1 jar from the OSGi R4.1 specification at They do not need to be a member, but they must fill out a form so an e-mail can be sent with special links to download the jars from OSGi.

Members can access the content or the OSGi R4.1 specification at The latest builds of the OSGi R4.2 specification can be accessed by members at

Platform Releng Helios Plan

Helios plan

Platform Indigo Plan

Indigo plan

How to assemble the deltapack using the p2 slicer

Create a build script that looks like this. This example is built using the 3.5RC2 bundles and 3.5RC2 p2 repository.

<project default="build">
	<target name="build">
		<property name="repo" value="" />
		<property name="tempDir" value="D:\\deltapack" />

		<p2.mirror source="${repo}">
			<destination kind="metadata" location="file://${tempDir}" name="RCP Delta Pack Repo" format="${repo}" />
			<destination kind="artifact" location="file://${tempDir}" name="RCP Delta Pack Repo" format="${repo}" />
			<iu id="" version="" />
			<iu id="" version="" />
			<iu id="" version="" />
			<iu id="org.eclipse.equinox.executable" version="" />
			<slicingOptions includeOptional="false" includeNonGreedy="false" followStrict="true" followOnlyFilteredRequirements="true" />

Unzip 3.5RC2 to a directory and run the script using the AntRunner.

D:\3.5RC2plugins\eclipse>java -jar plugins\org.eclipse.equinox.launcher_1.0.200. v20090520.jar -application org.eclipse.ant.core.antRunner -buildfile -d D:\temp\build.xml

The resulting files will be in the d:\deltapack directory on your file system.

How to verify the packed jars in a repo

java -cp plugins/org.eclipse.equinox.p2.jarprocessor_1.0.100.v20090520-1905.jar org.eclipse.equinox.internal.p2.jarprocessor.verifier.Verifier -dir <tempWorkingDir> <inputfolder>

Overview of JUnit4 changes released to Eclipse test framework in Eclipse 3.6M4

[Junit4 Changes]

How to avoid breaking the build

Avoid breaking the build

Submitting content to the Helios build

The helios build files are in in /cvsroot/callisto. We update the and files to reflect the versions of the components each milestones. This is the location of the milestones directory on the build machine.


I just ls the features directory of the current milestone, update the build files, then commit.

Invoking the signing process from the command line

  1. Login via ssh to and ensure you're in the signer's group (groups myuserid | grep signers)
  2. Copy the file you want to sign to the signing staging area. In our case, it's /home/data/httpd/download-staging.priv/eclipse
  3. Invoke the signing script as follows /usr/bin/sign /home/data/httpd/download-staging.priv/eclipse/ mail /home/data/httpd/download-staging.priv/eclipse/myOutput

Note: You're bundles don't have to be in zip file. You can also just sign an individual jar.

You'll receive an email when the signing is complete and available in /home/data/httpd/download-staging.priv/eclipse/myOutput

You can also tail -f /tmp/signing/signer.log to see the output as the bundles are signed.

Connecting to the derby database using ij

export JAVA_HOME=/builds/Cloudscape_10.0/ibm-jre-n142p/jre

export DERBY_HOME=/builds/db-derby-

cd /builds/db-derby-

connect 'jdbc:derby://localhost:1528/perfDb36';

Are the Eclipse and Equinox projects converting from CVS to git?

This was completed in the fall of 2012. Here's the planning document

Juno Git Migration

Here is the umbrella bug 345479 that was used to coordinate the migration.

How do you incorporate the p2MirrorURL into your repo at build time

See this excellent document p2.mirrorsURL written by Stephan Herrmann.

The p2.mirrorsURL should be added to your metadata so that p2 will see the list of available mirrors to choose during installation. Mirrors = less bandwidth utilization = happy webmasters. Always try to keep the sysadmins happy is my motto.

Eclipsecon presentations





Best releng practices from our Eclipsecon 2005 poster:

  1. Automate the build process from end-to-end and automate early.
  2. Use PDE Build in Eclipse to generate build scripts.
  3. Automate JUnit testing and performance monitoring.
  4. Automate build notifications (email).
  5. Use gentle humiliation to encourage developers to contribute carefully. (Clown nose technique.)
  6. Ensure stability in the build process by thorough testing of builder changes.
  7. Schedule builds at regular intervals and enforce rebuild policies.
  8. Use map files in a central CVS repository.
  9. Build on Linux.
  10. Have fun!

Useful reference documents

Who are the platform-releng committers?

Kim Moir

As the holiday season approaches, what gifts are appropriate for your favourite release engineer?

We enjoy fine chocolate, Shaan, and apple juice.

What does the platform-releng team do when they're not running the build farm and wrangling bugs?

We herd cats. s/eds/ibm/g

What factors contribute to the low percentage of women participating in free software/open source?

Cambridge University recently completed a study on this very topic with interesting results.

Here is another one written by Val Henson, a Linux kernel committer.

2008 report from Catalyst

Deprecated contents from Eclipse Platform Release Engineering FAQ

Old content from the faq can be found here

Back to the top