[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [wtp-dev] How to do local builds?
|
Jeff,
Releng project is tagged with every build (i.e. vS200509121958).
However, dependency scripts do not use CVS to get a build. They will
use an existing build. For example you can add something like this to a
properties file (you can find other examples in components folders and
distribution/wtp.tests ):
#######################################################################################
# WTPSDK Dependency
# wtp zip to be downloaded
# wtp SDK will be used for building
# groupID : wtp
wtp.url =
http://download.eclipse.org/webtools/downloads/drops/I-I20050916-200509160052
wtp.file=wtp-sdk-I20050916.zip
wtp.name = WTP SDK Build
wtp.description = Eclipse WebTools Platform
And have a dependency script like:
<?xml
version="1.0"?>
<project name="test" default="get">
<target name="get">
<antcall target="getAndInstall">
<param name="groupId" value="wtp" />
</antcall>
</target>
<target name="getAndInstall">
<ant antfile="${dependencyTargets}" target="checkDependency">
<property name="groupId" value="${groupId}" />
</ant>
<ant antfile="${dependencyTargets}" target="installDependency">
<property name="groupId" value="${groupId}" />
<property name="base.install.dir" value="${base.install.dir}" />
</ant>
</target>
</project>
And call it by setting the properties:
ant -Ddependency.properties=./myDependency.properties
-Dbase.install.dir=installHere -DdependencyTargets=[where teh releng
depenecy script is] -f myDependency.xml
Hi Naci,
Thanks for the thorough explaination. I'm interested in learning more
about the generic dependency scripts, the ones that install all the
prereqs for you. My understanding is that these scripts use the
information defined in the releng/maps/dependencies.properties file to
find out which version of the prereqs to install. Say I want to
reproduce last week's integration build, does that mean I should check
out the releng project tagged with last week's integration build's ID?
In another word, is the releng project tagged every build?
Thanks,
Jeff
*Naci Dai <naci.dai@xxxxxxxxxxxxx>*
Sent by: wtp-dev-bounces@xxxxxxxxxxx
09/20/2005 11:34 AM
Please respond to
naci.dai and "General discussion of project-wide or architectural issues."
To
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
cc
Subject
Re: [wtp-dev] How to do local builds?
Hi jeff,
The new builds are organized under 3 concepts: Components,
Distributables and Generic Scripts.
*
Components*: These build on the fine grain feature descriptions that
are being developed by David. Each "buildable" component will have
its folder under the components directory. This folder contains a
customTargets.xml, which is described in the PDE builds. When we run
the build for a components, the result is a zip that contains all the
features/plugins for that feature.
To run a component build, we use a generic build script and pass the
component name (i.e. *component=jst*) .
*
Distributable*: A distributable is a downloadbale drop for a project
build. Distributables are also named. For example, we have a
distributable called "wtp". A distributable must have a build, test,
site and an upload. These are scripts under the distributable
directory. Build determines what components are included in it (see
above). For example, wtp distributable have wst,wst-sdk, wst.test,
wst.perf.tests, jst, jst.sdk, jst.tests. jst.perf.tests). It uses
compoent build scripts. Test runs all automated tests to verify the
build. Site generates a website for the distributable drop. Upload
sends it to the download.eclipse.org.
To run a distributable build, we use a generic build script and pass
the distributable name (i.e. *distributable=wtp*). For example cruise
control calls distributable scripts with the name wtp.
*
Generic Scripts:* These are generic scripts that can be used by
component and/or distributable builds. By defining component and
distributable names and other build properties, these scripts can be
used by any component and distributable build without any change.
That is why we call them generic. Currently, there are generic
scripts for builds, dependencies, and monitoring. Build scripts are
for running PDE builds (i.e running a component build), they are used
for component builds. Dependency sscripst can be used by components
or distributables, provided a list of dependencies (see the scripts
and dependency.properties). They will download a dependency library
from internet, store it in a local repository, and install it into a
target directory. These are used to install drivers such as eclipse
sdk, emf, gef, jem, tomcat, jonas, piagent, oagis etc. Finally,
monitoring is used to send email messages of build progress.
The rough guideline for adding a generic scripts is that it should run
for any component or distributable by just setting a name. It should
not assume any relative directory structure. And it should not
include the sources for any "tooling", but can contain the binary for
the tools/tool-plugins. releng.wtpbuilder should not need any other
module to run or should not need to build itself first to run
something else. Tools will remain where they were, i.e.
releng.builder/tools.
I imagine performance and api-checks would be "distributable" level
scripts. However, we will not run them with every build. But this is
your area so I will leave that to you.
Hi Naci,
Do you have any documentation on how to do local builds and how to add
new "tasks" to the build (ex, performance and api)? Also, is there a
way to kick off the test phase without going through the build phase?
If so, how?
Thanks,
Jeff
------------------------------------------------------------------------
_______________________________________________
wtp-dev mailing list
_wtp-dev@eclipse.org_ <mailto:wtp-dev@xxxxxxxxxxx>
_https://dev.eclipse.org/mailman/listinfo/wtp-dev_
--
Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
_http://www.eteration.com/_
_mailto:nacidai@acm.org_
_mailto:naci@eteration.com________________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
------------------------------------------------------------------------
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
--
Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com/
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx