admin@glassfish.java.net

Admin devtests on Windows

From: Tom Mueller <tom.mueller_at_oracle.com>
Date: Fri, 15 Apr 2011 13:15:58 -0500

Admin team:

The admin devtests are running again on Windows. See
http://hudson-sca.us.oracle.com/job/admin-devtests-trunk-windows/ for
people internal to Oracle. There are currently 2443 testing passing
with no failures on Windows.

This job is running as a direct "ant" job rather than using the
hudson.sh script. To make this work, several changes have been
implemented in the build.xml:

1. There is now a "download" target that will download and install
glassfish from the continuous build. You can redefine the gfurl property
if you want glassfish.zip to come from somewhere else.

2. The env.S1AS_HOME, env.APS_HOME, and env.AS_LOGFILE properties can
now be passed into ant as properties rather than environment variables
if you wish. For example, the ant command that is run by the hudson job
is this:

ant -Denv.APS_HOME=../../.. -Dnum_tests=45 -Denv.AS_LOGFILE=../../../../glassfish3/glassfish/cli.log -Denv.S1AS_HOME=../../../../glassfish3/glassfish clean download all


3. There is now a "runtest" macro that replaces the call to "java" for
running tests. So now a typical test looks like this in the build.xml:

<target name="cluster" depends="init">
<runtest classname="admin.ClusterTest"/>
</target>

Please use this when adding new tests. The macrodef can be modified to
add additional parameters that should be passed to all tests. If you
need to pass special java arguments to your test, this can still be
done; see the "instance" test for an example. The main reason for
creating runtest was to make #2 work.

The unix hudson job is still using hudson.sh. This could be run with
ant too, but I haven't decided yet whether to change this. The one
thing that the ant version doesn't do is to kill any ASAdmin processes
that are hanging around before the test starts.

Have a nice weekend.
Tom