Difference between revisions of "Mylyn/Build Infrastructure"

Revision as of 19:02, 18 August 2015

This page describes how Mylyn is built and tested and how snapshot and release builds are published.

The Mylyn project uses two Hudson servers with the following major classes of build jobs:

http://ci.mylyn.org/

Hudson instance running on the same server that hosts the test repositories.

Build Jobs

• Provisioning jobs that provision the test repositories
• [*] Weekly version-specific integration builds that build and run all integration test fixtures on all supported Eclipse versions
• Nightly test builds that run one integration test fixture (1 build per connector)
• Nightly mylyn-all-snapshot that runs all integration test fixtures

https://hudson.eclipse.org/mylyn/

The Mylyn HIPP. There is some duplication with jobs on ci.mylyn.org because while those jobs are faster (due to co-location with test repositories), keep much longer histories, and tend to be more reliable, they cannot publish artifacts to download.eclipse.org and their test results are not linked from release builds.

Build Jobs

• Gerrit builds that verify Gerrit reviews. See Mylyn/Contributor_Reference#Hudson for information about the contributor whitelist.
• Nightly snapshot builds that run one integration test fixture and publish nightly snapshots (1 build per connector)
• [*] Integration build that builds and runs unit tests (no integration fixtures) against all supported Eclipse versions
• Integration-connectors build that runs all integration test fixtures
• Release builds that build and publish releases and trigger the integration builds

Scheduling

The release build for the current release runs weekly, and thus the integration and integration-connectors builds run weekly.

[*] indicates a matrix build

Snapshots

Nightly snapshots are published to http://download.eclipse.org/mylyn/snapshots/nightly/ by the Nightly builds. The Release builds publish releases and snapshots to http://download.eclipse.org/mylyn/drops. These snapshots are used to build SRs via composite sites like http://download.eclipse.org/mylyn/snapshots/3.14/.

Build Configuration

See Mylyn/FAQ#System_Properties for system properties used to control whether all fixtures are run and whether any are excluded.

Integration and release builds run against the parent git repository that includes all sub-projects as submodules.

Build Target Platforms

The matrix builds build Mylyn against different Eclipse versions. The mylyn-eX.Y targets are used to build against the latest Eclipse release in the given stream (e.g. 4.4.2, 4.5) or the latest milestone build of the upcoming release; mylyn-emaintenance is used to build against the latest candidate for the next Eclipse update release (e.g. 4.5.1); mylyn-estaging is used to build against the latest candidate for the next Eclipse major release (e.g. 4.6). The maintenance, staging, and latest X.Y targets build against the latest plugin versions available on the Eclipse platform update site, whereas the released X.Y targets build against specific versions in the release.

Once an update site is available for the upcoming major release, a new target should be created for that release, and axes should be added for that target to the matrix builds marked with [*] above:

• create target by copying the latest and changing the target name and file name
• change Eclipse Platform dependency versions to 0.0.0

Old axes should be removed once they are no longer supported, except for the Indigo axis because it is still the basis for a number of Eclipse-based products.

After RC4 (of a major or an update release), update versions of Eclipse Platform dependencies:

cd ~/releng/bin
./extractVersionsFromUpdateSite.sh ../../org.eclipse.mylyn-target/mylyn-e4.4.target ~/downloads/releases/luna/201409261001/ junit

Copy the desired suggestions to the target file. To get version for org.eclipse.sdk.ide (a product IU)

unzip ~/downloads/releases/luna/201409261001/content.jar; grep "id='org.eclipse.sdk.ide'" content.xml; rm content.xml