Jump to: navigation, search

Difference between revisions of "JWT Automatic Build"

(Adding new plugons to the JWT release)
(What we have)
Line 46: Line 46:
  
 
== What we have ==
 
== What we have ==
 +
 +
=== JWT build minimal Eclipse base ===
 +
 +
'''TODO'''
 +
 +
== How to use it ==
  
 
=== Update sites organisation ===
 
=== Update sites organisation ===

Revision as of 18:20, 5 January 2009

Automatic build of JWT Features and Plugins

Helpful resources

What we did

Pre-requirements

  • First, we downloaded CVS support for the command line: [CVS]
  • Afterwards, we downloaded PDE Releng:
       cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse export -r HEAD org.eclipse.releng.eclipsebuilder
  • We set some system variables, e.g. the ECLIPSE_HOME-variable:
       set ECLIPSE_HOME=C:\Programme\Eclipse //adapt to your Eclipse home directory
  • And also configured the Build target directory:
       set BUILD_HOME=C:\Build\New //adapt to your Build directory


Startup the build process

  • Generate a build.xml from the feature using right-click, PDE Build -> Generate Ant Script (this creates a build.xml in the feature directory)
  • Go to the directory of the feature: cd ...\jwt-we-feature
  • Execute:
      java -cp %ECLIPSE_HOME%\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar 
         org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner 
        -buildfile build.xml -Dcomponent=sdk.examples 
        -Dconfigs="*,*,*" 
        -Dbaseos=win32 
        -Dbasews=win32 -Dbasearch=x86 -Djavacfailonerror=true 
        -Dpde.build.scripts=%ECLIPSE_HOME%/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts 
        -DbaseLocation=%ECLIPSE_HOME% 
        -DbuildDirectory=&BUILD_HOME%
  • This generates the JAR-file of the feature.

What we have

JWT build minimal Eclipse base

TODO

How to use it

Update sites organisation

First, as it is the case in most of "one feature" projects (such as GEF), JWT now has 3 update sites:

Start a build for build.eclipse.org

Anyone who has access to build.eclipse.org can now start a build of cvs HEAD by typing from JWT home folder ./build.sh [buildType] where build type is I (default), S or R, respectively for integration, stable or release build.

This script will start the whole build process and update the update-site for the specified build type.

Start a build on your local machine

If you want to build locally JWT, simply checkout the org.eclipse.jwt/releng CVS module and write a script that starts the build with your local configuration (please do not modify build.sh or build.properties, that are build.eclipse.org files). See build.mistria.openwide.sh for example.

Continuous integration

TODO Note that the PDE build process supports unit testing. I've read about several Eclipse projects that used a continuous integration tool (such as cruise, continuum or hudson) to monitor their builds and test results. I'll try to choose if one of these solutions is fine for JWT.

Releasing Policy

When releasing JWT, here are the steps to follow:

  1. Tag the feature and all plugins included into the release with tag R{releaseVersion} (for example R0.5.0)
  2. Build on build.eclipse.org the feature to release (./build.sh R). The update site is automatically updated.
  3. Increment the feature version number (See Version Numbering)
  4. Increment all plugins versions that will be modified in next release)
  5. Create a buzz about this release!

Adding new plugons to the JWT release

TODO