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 "EASE/Build"

(Release Process)
Line 26: Line 26:
 
|[https://hudson.eclipse.org/ease/job/ease-build-branch/ ease-build-branch]
 
|[https://hudson.eclipse.org/ease/job/ease-build-branch/ ease-build-branch]
 
|Checks out a dedicated branch (set as parameter) and builds that branch. Typically triggered by other builds. May be triggered manually.
 
|Checks out a dedicated branch (set as parameter) and builds that branch. Typically triggered by other builds. May be triggered manually.
 +
 +
|-
 +
|[[File:Empty 32x32.png]] [[File:Empty 32x32.png]] [[File:Hudson.gif]] [[File:Empty 32x32.png]]
 +
|[https://hudson.eclipse.org/ease/job/ease-checkout-core/ ease-checkout-core]
 +
|Checks out the latest version of the [https://git.eclipse.org/r/#/admin/projects/ease/org.eclipse.ease.core core repository]. Only triggered by other builds.
 +
 +
|-
 +
|[[File:Empty 32x32.png]] [[File:Empty 32x32.png]] [[File:Hudson.gif]] [[File:Empty 32x32.png]]
 +
|[https://hudson.eclipse.org/ease/job/ease-checkout-modules/ ease-checkout-modules]
 +
|Checks out the latest version of the [https://git.eclipse.org/r/#/admin/projects/ease/org.eclipse.ease.modules modules repository]. Only triggered by other builds.
  
 
|-
 
|-

Revision as of 10:29, 9 February 2015

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

Hudson job setup.png


Scheduling Job Description
Empty 32x32.png Empty 32x32.png Hudson.gif Empty 32x32.png ease-base-build Builds a pre-configured workspace. Only triggered by other builds.
Ease user.png Empty 32x32.png Hudson.gif Empty 32x32.png ease-build-branch Checks out a dedicated branch (set as parameter) and builds that branch. Typically triggered by other builds. May be triggered manually.
Empty 32x32.png Empty 32x32.png Hudson.gif Empty 32x32.png ease-checkout-core Checks out the latest version of the core repository. Only triggered by other builds.
Empty 32x32.png Empty 32x32.png Hudson.gif Empty 32x32.png ease-checkout-modules Checks out the latest version of the modules repository. Only triggered by other builds.
Ease user.png Clock.png Empty 32x32.png Empty 32x32.png ease-nightly Builds from master branch and automatically promotes the update site to update/nightly. Update site gets replaced. Triggered nightly.
Ease user.png Empty 32x32.png Empty 32x32.png Empty 32x32.png ease-release Builds from a given branch. Needs manual promotion to publish update site to update/release. Update site is merged.
Ease user.png Clock.png Empty 32x32.png Empty 32x32.png ease-sonar Builds from master branch and analyses code for sonar integration. Triggered weekly.
Empty 32x32.png Empty 32x32.png Empty 32x32.png Gerrit.png 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.
Empty 32x32.png Empty 32x32.png Empty 32x32.png Gerrit.png 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:

  1. run ease-release on the Hudson server.
  2. on a failure: fix the problem, back to step 1
  3. 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.
  4. on a failure: fix the problem, back to step 1
  5. create a tag named release_${version} (eg release_0.5.3) for each of the following repositories:
  6. push created tags
  7. update plugin/feature versions to next revision (0.5.3 -> 0.6.0); also update org.eclipse.ease.releng/hudson/master.pom.xml version
  8. update the Release Notes wiki page
  9. update the download/index.php page location
  10. add a news entry to the news folder
  11. post an update to the mailing list

Back to the top