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.
Difference between revisions of "RAP/Build Process"
< RAP
(→Nightly Builds) |
(→Procedure for Milestone builds) |
||
Line 28: | Line 28: | ||
* Prepare new base platform in <code>/shared/rt/rap/base-platforms</code> (see <code>HOWTO</code> file) | * Prepare new base platform in <code>/shared/rt/rap/base-platforms</code> (see <code>HOWTO</code> file) | ||
* Configure pom.xml files to include the new base platform | * Configure pom.xml files to include the new base platform | ||
− | * Build runtime and tooling with <code>BUILD_TYPE</code> <code>S</code> for stable builds (these will be signed) | + | * Build runtime and tooling with <code>BUILD_TYPE</code> = <code>S</code> for stable builds (these will be signed) |
+ | * Move repositories to download area (see <code>/shared/rt/rap/publish/</code>) | ||
+ | * Contribute repositories to simrel aggregator | ||
* Add tag to git repositories | * Add tag to git repositories | ||
** Use annotated tags, pattern: <code>1.5.0-Mx-YYYYMMDD</code> | ** Use annotated tags, pattern: <code>1.5.0-Mx-YYYYMMDD</code> | ||
Line 40: | Line 42: | ||
* Announce via Blog | * Announce via Blog | ||
* Re-deploy demo applications (in oder to demonstrate the new features from the milestone) | * Re-deploy demo applications (in oder to demonstrate the new features from the milestone) | ||
+ | * Update composite repositories for runtime and tools | ||
* Update rap/latest-stable/{runtime/tooling} repositories to redirect to new repo (for compatibility with 1.4 tooling) | * Update rap/latest-stable/{runtime/tooling} repositories to redirect to new repo (for compatibility with 1.4 tooling) | ||
* Update rap/targets/ files | * Update rap/targets/ files |
Revision as of 14:06, 21 May 2012
Since version 1.5, RAP is built on the public build server at Eclipse.
Contents
Hudson Builds
Build jobs at the Eclipse.org Hudson:
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 cron job:
/shared/rt/rap/scripts/updateNightlyBuilds.sh
This job is run by rsternber's crontab.
Procedure for Milestone builds
- Prepare new base platform in
/shared/rt/rap/base-platforms
(seeHOWTO
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) - Move repositories to download area (see
/shared/rt/rap/publish/
) - Contribute repositories to simrel aggregator
- Add tag to git repositories
- Use annotated tags, pattern:
1.5.0-Mx-YYYYMMDD
- Use annotated tags, pattern:
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
- Notify the newsgroup
- Announce via Blog
- Re-deploy demo applications (in oder to demonstrate the new features from the milestone)
- Update composite repositories for runtime and tools
- 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 (
dev.eclipse.org:/home/data/httpd/archive.eclipse.org/rt/rap/downloads
), 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
andepl-v10.html
files for updates - Make sure
notice.html
andepl-v10.html
files are included in the download zip files (see bug 347659)