Eclipse Release Engineering build schedule

(Platform, JDT, PDE and Equinox)

static content last updated 2013-05-17

I-builds use branches specified in repositories.txt file, from master branch of aggregator (eclipse.platform.releng.aggregator). The projects built are submodules of aggregator so normally there is one line in repositories.txt file for each submodule of the aggregator.

N-builds always use 'master' branch of the repositories built.

M-builds use a branch of the aggregator (and therefore a branch of the repositories.txt file) and, like I-builds, pull whatever branch is specified in the repositories.txt file.

Rebuild Policy


Build Retention Policy

In an effort to reduce our disk utilization on the eclipse.org infrastructure and reduce the amount of data sent to the mirrors, we have adopted the following build retention policy.


Build Notes

For the 4.<n> Integration builds:
For the 4.<n-1>.x maintenance builds:

In the above descriptions, a build is considered to be a failure if there are "Red X"s that the developers agree represent valid reasons for them to not begin using the integration build. An example of a Red X which would *not* require a re-build would be a test which failed because the test was bogus.

IMPORTANT: This strategy requires us to have good build inputs. All teams must use the tools to pre-build and test their submissions. In addition, teams should track the nightly builds to detect integration problems early on. What we want to achieve is for the Tuesday morning 4.<n> build to typically be successful, with an infrequent requirement for a Wednesday noon build. Failing the Wednesday noon rebuild should be treated as a catastrophic failure. In other words, more than two or three of these per year is an unacceptable failure rate.