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.
EASE/Build
< EASE
Revision as of 07:08, 23 April 2015 by Christian.pontesegger.web.de (Talk | contribs) (→Release Process)
EASE is based on a maven/tycho build.
Manual Build
Integration Server
The main hudson integration server is available at: https://hudson.eclipse.org/ease/
Job Description
| Scheduling | Job | Description |
|---|---|---|
 
|
ease-base-build | Builds a pre-configured workspace. Only triggered by other builds. |
|
ease-build-branch | Checks out a dedicated branch (set as parameter) and builds that branch. Typically triggered by other builds. May be triggered manually. |
|
|
ease-checkout-core | Checks out the latest version of the core repository. Only triggered by other builds. |
|
|
ease-checkout-modules | Checks out the latest version of the modules repository. Only triggered by other builds. |
|
ease-nightly | Builds from master branch and automatically promotes the update site to update/nightly. Update site gets replaced. Triggered nightly. |
|
|
ease-release | Builds from a given branch. Needs manual promotion to publish update site to update/release. Update site is merged. |
|
|
ease-sonar | Builds from master branch and analyses code for sonar integration. Triggered weekly. |
|
ease-verify-core | Verifies gerrit commits on ease.core repository. Builds and tests against ease.modules [master]. Provides +1/-1 to gerrit commits. Only triggered by gerrit. |
|
|
ease-verify-modules | Verifies gerrit commits on ease.modules repository. Builds and tests against ease.core [master]. Provides +1/-1 to gerrit commits. Only triggered by gerrit. |
Release Process
Maintain Bugtracker:
- verify that bugs are in CLOSED state and not ony RESOLVED
- verify that Target Milestone is set to the upcoming release name
Maintain Release Description:
- switch to https://projects.eclipse.org/projects/technology.ease
- open the upcoming release and maintain release information
Follow the Eclipse release process:
- create an automated IP Log for EASE
- verify that the log is correct and send it by pushing Submit The Log at the bottom of the page
- send an email to technology-pmc@eclipse.org, requesting release approval
Schedule the review (Review Process):
- schedule the review by sending email to emo@eclipse.org
- wait for the review approval
Create & update release binaries:
- run ease-release on the Hudson server.
- on a failure: fix the problem, back to step 1
- promote the build and set the version parameter correctly (eg 0.5.3). After promotion the update sites and download locations are updated and live.
- on a failure: fix the problem, back to step 1
- create a tag named release_${version} (eg release_0.5.3) for each of the following repositories:
- push created tags
- update the Release Notes wiki page
- update the download/index.php page location
- add a news entry to the news folder
- post an update to the mailing list
Prepare next release:
- update plugin/feature versions to next revision (0.5.3 -> 0.6.0); also update org.eclipse.ease.releng/hudson/master.pom.xml version
- create a new release on the EASE project page (sidebar: Committer Tools)
- create a new release & target on bugzilla