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.
Difference between revisions of "EASE/Build"
< EASE
Line 70: | Line 70: | ||
# update the [http://git.eclipse.org/c/www.eclipse.org/ease.git/tree/download/index.php download/index.php] page location | # update the [http://git.eclipse.org/c/www.eclipse.org/ease.git/tree/download/index.php download/index.php] page location | ||
# add a news entry to the [http://git.eclipse.org/c/www.eclipse.org/ease.git/tree/news news folder] | # add a news entry to the [http://git.eclipse.org/c/www.eclipse.org/ease.git/tree/news news folder] | ||
+ | # post an update to the [https://dev.eclipse.org/mailman/listinfo/ease-dev mailing list] | ||
[[Category:EASE]] | [[Category:EASE]] |
Revision as of 17:35, 21 December 2014
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-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
After following the Eclipse Release Guidelines do:
- 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