Skip to main content
Jump to: navigation, search

Difference between revisions of "RAP/Build Process"

(Hudson Builds)
Line 3: Line 3:
=== Hudson Builds ===
=== Hudson Builds ===
We have two build jobs at the Hudson:
Build jobs at the Hudson:
* [ rap-runtime]
* [ rap-1.5-runtime]
* [ rap-tooling]
* [ rap-1.5-tools]
* [ rap-1.5-incubator]
The base directory for our builds is <code>/shared/rt/rap</code> on <code></code>.
The base directory for our builds is <code>/shared/rt/rap</code> on <code></code>.

Revision as of 10:36, 17 May 2012

Since version 1.5, RAP is built on the public build server at Eclipse.

Hudson Builds

Build jobs at the Hudson:

The base directory for our builds is /shared/rt/rap on

Nightly Builds

We produce a p2 repositories from our nightly builds:

These p2 repositories are updated by a cron job:


This job is run by rsternber's crontab.

Procedure for Milestone builds

  • Prepare new base platform in /shared/rt/rap/base-platforms (see HOWTO file)
  • Configure pom.xml files to include the new base platform
  • Build runtime and tooling with BUILD_TYPE S for stable builds (these will be signed)
  • Add tag to git repositories
    • Use annotated tags, pattern: 1.5.0-Mx-YYYYMMDD


  • Finalize New & Noteworthy
  • Update web site: builds.xml and arrivals sidebar
  • Scan Bugzilla for open bugs that are targeted at the milestone or bugs that are still open but solved, verify target version of closed bugs
  • Notify the newsgroup
  • Announce via Blog
  • Re-deploy demo applications (in oder to demonstrate the new features from the milestone)
  • Update rap/latest-stable/{runtime/tooling} repositories to redirect to new repo (for compatibility with 1.4 tooling)
  • Update rap/targets/ files

Procedure for release builds

additional steps to do when creating release builds

  • ensure version numbers in bundle manifests
  • ensure legal files (see [1])
    • check that about.html are included in source build
  • update infocenter content and links to infocenter from project home page
  • update help plugin
  • Check copyright year and version number of JavaDoc (search for "JavaDoc" in org.eclipse.rap.releng/tooling/customTargets.xml)
  • Move old builds to archive (, update archive page
  • Update the RAP-tooling entry in the Eclipse Marketplace and in the Yoxos Marketplace. They should point to the latest release. (Beyhan)
  • Redirect rap/latest-release/{runtime/tooling} repositories
  • notify newsgroup and mailing list
  • use the portal to review project metadata that is displayed in the "About this Project" page (i.e. update release train name in description text)
  • Check notice.html and epl-v10.html files for updates
  • Make sure notice.html and epl-v10.html files are included in the download zip files (see bug 347659)

Simultaneous Release

Back to the top