Jump to: navigation, search

Difference between revisions of "Gyrex/Contributor Guide/Builds"

(New page: Gyrex builds are produced on the Eclipse.org infrastructure. It's also possible to build locally. == RelEng Project == The root for all build related stuff is the Gyrex RelEng (Release En...)
 
Line 2: Line 2:
  
 
== RelEng Project ==
 
== RelEng Project ==
The root for all build related stuff is the Gyrex RelEng (Release Engineering) project.
+
The root for all build related stuff is the Gyrex RelEng (Release Engineering) project. It contains [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/builder/?root=Technology_Project build scripts], [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/maps/?root=Technology_Project map files], [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/targets/?root=Technology_Project target platform definitions] and [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/products/?root=Technology_Project product configurations].
 
<pre>
 
<pre>
 
:pserver:anonymous@dev.eclipse.org:/cvsroot/technology/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng
 
:pserver:anonymous@dev.eclipse.org:/cvsroot/technology/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng
 
</pre>
 
</pre>
  
It contains [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/builder/?root=Technology_Project build scripts], [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/maps/?root=Technology_Project map files], [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/targets/?root=Technology_Project target platform definitions] and [http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng/products/?root=Technology_Project product configurations].
+
== Build Process ==
 +
The build process is entirely based on PDE Build (which is based on Ant). The main build script includes targets for calling from a plain Ant as well as from an Eclipse Ant. The plain Ant target bootstraps a PDE Builder from Eclipse CVS and then launches the Eclipse target using Eclipse Ant. There is also a shared external tool launch configuration that can be used for building from within Eclipse.
 +
 
 +
The build process if as follows:
 +
* Bootstrap PDE Builder
 +
* Fetch sources using map files
 +
* Build org.eclipse.gyrex.features.master
 +
* Assemble Gyrex Server Product
 +
* Produce final p2 Repo (including signing of artifacts when executed on Eclipse.org infrastructure)
 +
* Publish to download.eclipse.org (when executed on Eclipse.org infrastructure)
  
 
== Hudson Build Jobs ==
 
== Hudson Build Jobs ==

Revision as of 05:25, 4 March 2011

Gyrex builds are produced on the Eclipse.org infrastructure. It's also possible to build locally.

RelEng Project

The root for all build related stuff is the Gyrex RelEng (Release Engineering) project. It contains build scripts, map files, target platform definitions and product configurations.

:pserver:anonymous@dev.eclipse.org:/cvsroot/technology/org.eclipse.gyrex/releng/org.eclipse.gyrex.releng

Build Process

The build process is entirely based on PDE Build (which is based on Ant). The main build script includes targets for calling from a plain Ant as well as from an Eclipse Ant. The plain Ant target bootstraps a PDE Builder from Eclipse CVS and then launches the Eclipse target using Eclipse Ant. There is also a shared external tool launch configuration that can be used for building from within Eclipse.

The build process if as follows:

  • Bootstrap PDE Builder
  • Fetch sources using map files
  • Build org.eclipse.gyrex.features.master
  • Assemble Gyrex Server Product
  • Produce final p2 Repo (including signing of artifacts when executed on Eclipse.org infrastructure)
  • Publish to download.eclipse.org (when executed on Eclipse.org infrastructure)

Hudson Build Jobs

The nightly job is used for CI compile check builds. It monitors the full source tree for changes and kicks of a build every once in a while when somebody checked something into source control. However, it always uses HEAD when performing checkouts. The build results should not be used.

The integration job is used for producing I, S and R builds. Care must be taken when producing S and R builds. The results are automatically published to download.eclipse.org (when running on Eclipse.org infrastructure).