Skip to main content
Jump to: navigation, search

Difference between revisions of "WTP/Build/WTP Batch Build"

< WTP‎ | Build
Line 41: Line 41:
:a. In <BUILD HOME>/releng.control/
:a. In <BUILD HOME>/releng.control/
:b. ./ –f cc_project_build.xml –Dprojectname=wtp-R3.0-I
:b. <b>./ –f cc_project_build.xml –Dprojectname=wtp-R3.0-I</b>
::Note:  projectname is mandatory, all available projects are
::Please note that <b>projectname</b> is mandatory, all available projects are:
:::wtp-R3.0-I for current 3.0 integration build
:::wtp-R3.0-I for current 3.0 integration build
:::wtp-R2.0-M for 2.0.2 maintenance build
:::wtp-R2.0-M for 2.0.2 maintenance build

Revision as of 15:06, 4 February 2008

How to setup WTP batch Build locally

1. Setup prereqs

a. apache ant 1.7 =>
b. Java SDK 1.4 and 1.5

2. Check out build files

mkdir <BUILD HOME>, for example mkdir /shared/webtools
checkout the releng.control project from CVS using the below command
cvs -Q -f -d export -d <BUILD HOME>/releng.control -r HEAD webtools.releng/releng.control
You should see the releng.control dir created in the <BUILD HOME> dir after running this command

3. Modifying properties files for your local build environment (you can do this either in eclipse or by opening the files from command line)

a. You can always get a fresh copy of all properties files from CVS by running the <BUILD HOME>/releng.control/ script, however to avoid your already modified properties files from being overwritten when the command is executed, you should make a copy of the properties directory first and modify the copied version
e.g. cp –R <BUILD HOME>/releng.control/localBuildExample ../new_props
b. Modifying <BUILD HOME>/releng.control/commonVariations.shsource
BUILD_HOME to location of where your java and ant
ANT_HOME to location of where your ant
JAVA_4_HOME to location of where your java 4
JAVA_5_HOME to location of where your java 5
LOCAL_BUILD_PROPERTIES_DIR to the copied properties directory from the last step
c. Modyfing <BUILD HOME>/new_props/
Update this file to point the java locations to where the JAVA prereqs you've created in step 1

4. Running the build:

a. In <BUILD HOME>/releng.control/
b. ./ –f cc_project_build.xml –Dprojectname=wtp-R3.0-I
Please note that projectname is mandatory, all available projects are:
wtp-R3.0-I for current 3.0 integration build
wtp-R2.0-M for 2.0.2 maintenance build
wtp-R3.0-N HEAD build for 3.0

5. Checking the build results

After the build is done, you should find the following directories created inside the <BUILD HOME> directory:basebuilders
Resulting Directories Description
basebuilders build plugins used from eclipse
committers final output of the log files
logcache used to generate log files
logs used to generate log files
prereqCache storage location for wtp build prereq files
projectBuilders projects used to build
projects wtp projects built, final build output
tests test results
releng.control This is the original directory checked out from CVS in step 2, and the build staring directory
new_props This is the properties directory created in step 3a, storing all of the properties files

Viewing the results

1. Run <workspace dir>/releng.control/./ to retrieve the necessary files from CVS to display results

2. Setup alias on linux to work with default webserver

i./sbin/service httpd start to start webserver and ensure http://localhost can be accessed post starting webserver
ii.Modify /etc/http/conf/httpd.conf to setup alias to your <BUILD HOME dir>
Alias /wtpbuild/ <BUILD HOME dir>/
<Directory "<Build Home dir> /">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
iii. Restart webserver to pick up changes /sbin/service httpd restart
iv. http://localhost/wtpbuild should bring up the index.php file where you can view the build and test results

Back to the top