Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Mylyn/Build Infrastructure"

Line 11: Line 11:
 
* [http://ci.mylyn.org/view/Provisioning/ Provisioning jobs] that provision the test repositories
 
* [http://ci.mylyn.org/view/Provisioning/ Provisioning jobs] that provision the test repositories
 
* [http://ci.mylyn.org/view/Integration/ Weekly version-specific integration builds] that build and run all integration test fixtures on all supported Eclipse versions
 
* [http://ci.mylyn.org/view/Integration/ Weekly version-specific integration builds] that build and run all integration test fixtures on all supported Eclipse versions
* [http://ci.mylyn.org/view/Snapshots/ Nightly test builds] that run one integration test fixture for each repository
+
* [http://ci.mylyn.org/view/Snapshots/ Nightly test builds] that run one integration test fixture (1 build per connector)
 +
* [http://ci.mylyn.org/job/mylyn-all-snapshot/ mylyn-all-snapshot] that runs all integration test fixtures
  
 
=== https://hudson.eclipse.org/hudson/ ===
 
=== https://hudson.eclipse.org/hudson/ ===
Line 17: Line 18:
 
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.
 
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 ====
 
==== Build Jobs ====
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Nightly/ Nightly builds] that run one integration test fixture for each repository and publish snapshots to http://download.eclipse.org/mylyn/drops/
+
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Nightly/ Nightly builds] that run one integration test fixture and publish snapshots to http://download.eclipse.org/mylyn/drops/ (1 build per connector)
 
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Integration/job/mylyn-integration/ Integration build] that builds and runs unit tests (no integration fixtures) against all supported Eclipse versions
 
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Integration/job/mylyn-integration/ Integration build] that builds and runs unit tests (no integration fixtures) against all supported Eclipse versions
 
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Integration/job/mylyn-integration-connectors/ Integration-connectors build] that runs all integration test fixtures
 
* [https://hudson.eclipse.org/hudson/user/spingel/my-views/view/Mylyn%20Integration/job/mylyn-integration-connectors/ Integration-connectors build] that runs all integration test fixtures

Revision as of 19:42, 20 October 2014


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

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

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

The Mylyn HIPP instance

Build Jobs

Build Configuration

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

Back to the top