RAP/Build Process

Since version 1.5, RAP is built on the public Hudson build servers at Eclipse.org.

Hudson Builds

From RAP version 2.1 on all RAP build jobs are running on a dedicated RAP Hudson instance:

Need help with older versions of Eclipse? Request Long Term Support (LTS).

RAP 1.5	RAP 2.0	RAP 2.1	RAP 2.2	RAP 2.3	RAP 3.x (head)
rap-1.5-runtime	rap-2.0-runtime	rap-2.1-runtime LTS	rap-2.2-runtime	rap-2.3-runtime LTS	rap-head-runtime
rap-1.5-tools	rap-2.0-tools	rap-2.1-tools	rap-2.2-tools	rap-2.3-tools	rap-head-tools
rap-1.5-incubator					rap-head-incubator-COMPONENT_NAME

The base directory for our builds is /shared/rt/rap on build.eclipse.org.

Nightly Builds

We produce p2 repositories from our nightly builds:

• http://download.eclipse.org/rt/rap/nightly/runtime/
• http://download.eclipse.org/rt/rap/nightly/tooling/

These p2 repositories are updated by a rap-head-publish job that runs after the master jobs are run.

Procedure for Milestone builds

• Prepare new base platform in /shared/rt/rap/base-platforms (see HOWTO.create file)
• Configure pom.xml files to include the new base platform
  • RAP Runtime
    • releng/org.eclipse.rap.build/pom.xml: base-platform-mars property and base-platform-repository repository
    • releng/org.eclipse.rap.build/repository.mars/pom.xml: base-platform-repository-with-ICU-bundle repository
    • features/org.eclipse.rap.equinox.target.feature/pom.xml: base-platform-repository-with-ICU-bundle
    • Enforce generation of new qualifier by "touching" features/org.eclipse.rap.equinox.target.feature/.forceQualifierUpdate
  • RAP Tools
    • Update target definition in releng/org.eclipse.rap.tools.build/target.definition/org.eclipse.rap.tools.target.definition.target
    • Enforce generation of new qualifier by "touching" features/org.eclipse.rap.tools.feature/.forceQualifierUpdate
• Build RAP Runtime two times, one time with BUILD_TYPE = S (signing, without tests), and another time with BUILD_TYPE = N (unsigned, with tests). Build RAP Tools.
• Move repositories to download area (see /shared/rt/rap/publish/)
• Contribute repositories to simrel aggregator
  • In most cases it is required to disable the Scout RAP contribution because of conflicting dependencies. The Scout project enables its contribution a day later when they contribute their updated build.
• Add tag to git repositories
  • TAG=3.0.0-Mx
  • git tag -a -m "$TAG" -s $TAG (note: -s creates a signed tag)
  • git push --tags origin
• Upload RWT bundles to Maven Central repository.

Publishing

• 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
• Update composite repositories for runtime and tools
• Update rap/targets/ files
• [1.5 only] Update rap/latest-stable/{runtime/tooling} repositories to redirect to new repo (for compatibility with 1.4 tooling)
• Notify the newsgroup
• Announce via Blog
• Re-deploy demo applications (in oder to demonstrate the new features from the milestone)

• Publish RWT bundles in the Maven Central repository.

Procedure for release builds

Additional steps to do when creating release builds and publishing them.

• ensure version numbers in bundle manifests and features are correct, qualifiers got updated
• ensure legal files (see [1])
  • check that about.html are included in source build
• update [help.eclipse.org/ infocenter] content and links to infocenter from project home page
• update help plugin and developers guide
• Check copyright year and version number of JavaDoc (search for "JavaDoc" in org.eclipse.rap.releng/tooling/customTargets.xml)
• Move old builds to archive (dev.eclipse.org:/home/data/httpd/archive.eclipse.org/rt/rap/downloads), update archive page
• Update the RAP-Tools entry in the Eclipse Marketplace. It should list the latest release.
• Redirect rap/latest-release/{runtime/tooling} repositories
• notify newsgroup and rap-dev 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)
• Add p2.stats to artifact.xml
• Add p2 mirror URLs to artifact.xml

• 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)

• Publish RWT bundles in the Maven Central repository.
• Publish updated Docker images with the RAP demo applications to registry.hub.docker.com
• Update the source code location for automated Eclipse Babel translations

Eclipse Marketplace

Make sure the RAP Tools are uploaded to the Eclipse market place.

Simultaneous Release

• Mars Aggregator
• Simultaneous_Release_FAQ

RAP Incubator Builds

In order to help early adopters consuming the work from the RAP Incubator project, we are running a set of automated builds from Git HEAD for all RAP Incubator Projects. Every component has its own build that must follow some common naming conventions.

• Every RAP Incubator Component has a COMPONENT_NAME, that is used to find the necessary build scripts, features, etc.
• Every component has its own Git repository org.eclipse.rap.incubator.COMPONENT_NAME.git at git.eclipse.org/c/rap/incubator/.
• The build is based on Tycho and uses the RAP Incubator parent releng/org.eclipse.rap.incubator.releng/pom.xml.
• The main build project releng/org.eclipse.rap.COMPONENT_NAME.build of the component contains the pom.xml that is used to build the entire component. In addition to that, it has
  • a repository/ sub-directory with an additional pom that creates the final p2 repository of the component.
• There is a main feature features/org.eclipse.rap.COMPONENT_NAME.feature that assembles everything that is used by a potential consumer.

Every build creates an independent p2 repository. All repositories are available on the build server at

/shared/rt/rap/incubator/nightly/COMPONENT_NAME

At the moment, we are running builds for the following components

• clientscripting
• cnf
• dropdown
• fileupload
• gef
• nebula-grid
• osgi-packaging
• pde
• richtext
• tabbed-properties
• visualization

and make them available from build.eclipse.org/rt/rap/incubator/nightly and from download.eclipse.org/rt/rap/incubator/nightly.