Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Mylyn/Build Infrastructure
This page describes how Mylyn is built and tested and how snapshot and release builds are published.
The Mylyn project uses three 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 for each repository
https://hudson.eclipse.org/hudson/
Eclipse Hudson server. There is some duplication with jobs on ci.mylyn.org because while those jobs are faster (due to co-location with test repositories) 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
- Nightly builds that run one integration test fixture for each repository and publish snapshots to http://download.eclipse.org/mylyn/drops/
- 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
https://hudson.eclipse.org/mylyn/
The Mylyn HIPP instance
Build Jobs
- Gerrit builds that verify Gerrit reviews
Build Configuration
See Mylyn/FAQ#System_Properties for system properties used to control whether all fixtures are run and whether any are excluded.