ViPER IDE RelEng

From ViPER Wiki

The Release Engineering component is used to support the headless build of the ViPER IDE, ViPER IDE Tests and ViPER IDE Enablers components.

Contents 1 ViPER IDE RelEng Distilled 2 Setup ViPER IDE RelEng 3 Possible problems 4 List of possible build process improvements 5 Things to check when compiling against a new build of Eclipse SDK 6 Build Process Debugging

[edit] ViPER IDE RelEng Distilled

A detailed explanation of the ViPER IDE RelEng project design can be found under ViPER IDE RelEng Distilled.

[edit] Setup ViPER IDE RelEng

1. Download the required JRE Versions (1.3.1, 1.4.2, 1.5.0, 1.6.0).
   • Extract them into a Java directory and create appropriate symbolic links (or rename the subdirectories), so that the directory content is as follows:
     • jre1.3.1
     • jre1.4.2
     • jre1.5.0
     • jre1.6.0
2. Create .cvspass file in your user dir by executing cvs -d :pserver:username@dev.viper.sc:/home/viper/cvs login (if you don't want to be prompted for CVS password during build process)
3. Download and unzip Eclipse SDK (or ViPER IDE)
4. Create new build workspace directory
5. Start eclipse/ViPER on that build workspace (-data)
   1. Checkout org.eclipse.releng.basebuilder into build workspace
   2. Download and unzip svn-pde-build plugin from http://sourceforge.net/projects/svn-pde-build) into workspace (it deploys itself into basebuilder plugin)
   3. Checkout sc.viper.ide.releng into build workspace
6. Modify the sc.viper.ide.releng/configurationFiles/serverConfiguration.properties file
   1. set your local java directory in the setting javaDirectory
   2. enter your own cvs user name
   3. set your local publishing directory
7. Move into sc.viper.ide.releng/scripts folder and call appropriate run script (1 GB free disk space required!).

[edit] Possible problems

• If the X server hangs during the UI test phase, the fvwm2 configuration is probably incorrect (/etc/X11/fvwm2), it should be empty (delete files in /etc/X11/fvwm2)(see http://bugs.viper.sc/show_bug.cgi?id=46)

[edit] List of possible build process improvements

1. Add Testing and Performance Tools Project / Metric tools to build process
   1. Code Coverage
   2. GUI Tests

[edit] Things to check when compiling against a new build of Eclipse SDK

• update the settings for the different build scripts in the configurationFiles directory

[edit] Build Process Debugging

Add

 <record name="temp.log" loglevel="verbose"/>

to /org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build/scripts/productBuild/productBuild.xml at start