Difference between revisions of "RAP/Build Process"

Revision as of 14:50, 20 February 2013

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

Prepare new base platform in /shared/rt/rap/base-platforms (see HOWTO file)
Configure pom.xml files to include the new base platform
- releng/org.eclipse.rap.build/pom.xml (RAP Runtime)
- releng/org.eclipse.rap.target.build/pom.xml (RAP Runtime)
- releng/org.eclipse.rap.tools.build/pom.xml (RAP Tools)
Build RAP Runtime and RAP Tools 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
- TAG=1.5.0-Mx-YYYYMMDD
- git tag -a -m "$TAG" -s $TAG (note: -s creates a signed tag)
- git push --tags origin

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

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

Eclipse Marketplace

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

Simultaneous Release

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
fileupload
gef
nebula-grid
osgi-packaging
pde
tabbed-properties
visualization

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

@@ Line 4: / Line 4: @@
 Build jobs at the Eclipse.org Hudson:
-* [https://hudson.eclipse.org/hudson/job/rap-1.5-runtime/ rap-1.5-runtime]
-* [https://hudson.eclipse.org/hudson/job/rap-1.5-tools/ rap-1.5-tools]
-* [https://hudson.eclipse.org/hudson/job/rap-1.5-incubator/ rap-1.5-incubator]
-* [https://hudson.eclipse.org/hudson/job/rap-2.0-runtime/ rap-2.0-runtime]
+{| border="1"
-* [https://hudson.eclipse.org/hudson/job/rap-2.0-tools/ rap-2.0-tools]
+|-
-* [https://hudson.eclipse.org/hudson/job/rap-2.0-incubator/ rap-2.0-incubator]
+! RAP 1.5 !! RAP 2.0 !! RAP 2.x (head)
+|-
+| [https://hudson.eclipse.org/hudson/job/rap-1.5-runtime/ rap-1.5-runtime]
+| [https://hudson.eclipse.org/hudson/job/rap-2.0-runtime/ rap-2.0-runtime]
+| [https://hudson.eclipse.org/hudson/job/rap-head-runtime/ rap-head-runtime]
+|-
+| [https://hudson.eclipse.org/hudson/job/rap-1.5-tools/ rap-1.5-tools]
+| [https://hudson.eclipse.org/hudson/job/rap-2.0-tools/ rap-2.0-tools]
+| [https://hudson.eclipse.org/hudson/job/rap-head-tools/ rap-head-tools]
+|-
+| [https://hudson.eclipse.org/hudson/job/rap-1.5-incubator/ rap-1.5-incubator]
+|
+| [https://hudson.eclipse.org/hudson/ rap-head-incubator-COMPONENT_NAME]
+|}
 The base directory for our builds is <code>/shared/rt/rap</code> on <code>build.eclipse.org</code>.
@@ Line 21: / Line 31: @@
 These p2 repositories are updated by a cron job:
-  /shared/rt/rap/scripts/updateNightlyBuilds.sh
+  /shared/rt/rap/scripts/publish-nightly-build.sh
 This job is run by rsternber's crontab.
@@ Line 28: / Line 38: @@
 * 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
-* Build runtime and tooling with <code>BUILD_TYPE</code> = <code>S</code> for stable builds (these will be signed)
+** <code>releng/org.eclipse.rap.build/pom.xml</code> (RAP Runtime)
+** <code>releng/org.eclipse.rap.target.build/pom.xml</code> (RAP Runtime)
+** <code>releng/org.eclipse.rap.tools.build/pom.xml</code> (RAP Tools)
+* Build RAP Runtime and RAP Tools 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
-** Use annotated tags, pattern: <code>1.5.0-Mx-YYYYMMDD</code>
+** <code>TAG=1.5.0-Mx-YYYYMMDD</code>
+** <code>git tag -a -m "$TAG" -s $TAG</code> (note: -s creates a signed tag)
+** <code>git push --tags origin</code>
 ==== Publishing ====
@@ Line 39: / Line 54: @@
 * 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)
-* 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)
+* Publish RWT bundles in the [[RAP/Maven_Central | Maven Central repository]].
-* Update rap/targets/ files
 === Procedure for release builds ===
@@ Line 57: / Line 74: @@
 * Check copyright year and version number of JavaDoc (search for "JavaDoc" in <code>org.eclipse.rap.releng/tooling/customTargets.xml</code>)
 * Move old builds to archive (<code>dev.eclipse.org:/home/data/httpd/archive.eclipse.org/rt/rap/downloads</code>), update archive page
-* Update the RAP-tooling entry in the [http://marketplace.eclipse.org/content/rich-ajax-platform-rap-tooling Eclipse Marketplace] and in the Yoxos Marketplace. They should point to the latest release. (Beyhan)
+* Update the RAP-tooling entry in the [http://marketplace.eclipse.org/content/rich-ajax-platform-rap-tooling Eclipse Marketplace] and in the Yoxos Marketplace. They should point to the latest release.
 * 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)
+* Add p2.stats to artifact.xml
+* Add p2 mirror URLs to artifact.xml
 * Check <code>notice.html</code> and <code>epl-v10.html</code> files for updates
 * Make sure <code>notice.html</code> and <code>epl-v10.html</code> files are included in the download zip files (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=347659 bug 347659])
+* Publish RWT bundles in the [[RAP/Maven_Central | Maven Central repository]].
+==== Eclipse Marketplace ====
+Make sure the RAP Tools are uploaded to the Eclipse market place.
 === Simultaneous Release ===
-* [https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/indigo.runAggregator/ indigo aggregator]
+* [https://hudson.eclipse.org/hudson/job/simrel.juno.runAggregator/ Juno Aggregator]
+* [https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/ Kepler Aggregator]
 * [[SimRel/Simultaneous_Release_FAQ|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 [http://www.eclipse.org/rap/incubator/ RAP Incubator Projects]. Every component has its own build that must follow some common naming conventions.
+* Every RAP Incubator Component has a <code>COMPONENT_NAME</code>, that is used to find the necessary build scripts, features, etc.
+* Every component has its own Git repository <code>org.eclipse.rap.incubator.COMPONENT_NAME.git</code> at [http://git.eclipse.org/c/rap/incubator/ git.eclipse.org/c/rap/incubator/].
+* The build is based on Tycho and uses the RAP Incubator parent [http://git.eclipse.org/c/rap/incubator/org.eclipse.rap.incubator.releng.git/tree/releng/org.eclipse.rap.incubator.releng/pom.xml releng/org.eclipse.rap.incubator.releng/pom.xml].
+* The main build project <code>releng/org.eclipse.rap.COMPONENT_NAME.build</code> of the component contains the <code>pom.xml</code> that is used to build the entire component. In addition to that, it has
+** a <code>repository/</code> sub-directory with an additional pom that creates the final p2 repository of the component.
+* There is a main feature <code>features/org.eclipse.rap.COMPONENT_NAME.feature</code> 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
+<code>/shared/rt/rap/incubator/nightly/COMPONENT_NAME</code>
+At the moment, we are running builds for the following components
+* clientscripting
+* cnf
+* fileupload
+* gef
+* nebula-grid
+* osgi-packaging
+* pde
+* tabbed-properties
+* visualization
+and make them available from [http://build.eclipse.org/rt/rap/incubator/nightly/ build.eclipse.org/rt/rap/incubator/nightly] and from [http://download.eclipse.org/rt/rap/incubator/nightly/ download.eclipse.org/rt/rap/incubator/nightly].

RAP 1.5	RAP 2.0	RAP 2.x (head)
rap-1.5-runtime	rap-2.0-runtime	rap-head-runtime
rap-1.5-tools	rap-2.0-tools	rap-head-tools
rap-1.5-incubator		rap-head-incubator-COMPONENT_NAME

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"

Revision as of 14:50, 20 February 2013

Contents

Hudson Builds

Nightly Builds

Procedure for Milestone builds

Publishing

Procedure for release builds

Eclipse Marketplace

Simultaneous Release

RAP Incubator Builds

Breadcrumbs

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"

Revision as of 14:50, 20 February 2013

Contents

Hudson Builds

Nightly Builds

Procedure for Milestone builds

Publishing

Procedure for release builds

Eclipse Marketplace

Simultaneous Release

RAP Incubator Builds