If there is a need to establish short integrity cycle which ensures that
the code is compliable and basic functionality is not broken. Then such
cycle can be organized in pretty straightforward way. Let’s take EHWA-API
as test scenario and run it on DRLVM:

1) Install the same tools,
as for building the Apache Harmony components.

These steps launches CruiseControl with
Class library, DRLVM and EHWA-API test scenario.
Alerts notifications are sent to specified
${framework.parameters.usemail.to} and test results can
be found in ${framework.parameters.optional.upload.dir}
The testing cycle is triggered by update of Class library or
DRLVM source code in
SVN repository.

Let's setup integrity cycle which is targeted to catch regression early.
So the cycle is based on HDK and runs unit tests from Class library,
DRLVM and JDKTools workspaces. Also let's optimize disk space usage and
run unit suites in built HDK workspace (by default they are checked out
to a separate workspace)

1) Install the same tools,
as for building the Apache Harmony components.

These steps launches CruiseControl that build HDK
and runs unit tests. The testing cycle is triggered by update of HDK
source code in
SVN repository.
Alerts notifications are sent to specified
${framework.parameters.usemail.to} and test results can
be found in ${framework.parameters.optional.upload.dir}