The Schmant plugin enables Hudson to run Schmant build scripts.

Requirements

• A Schmant installation, version 1.0.1 or newer.
• Hudson 1.337 or newer.
• That Hudson is run on a version 6 or newer JDK (since Schmant is run in the Hudson process).

Global configuration

Schmant home

The Schmant home property should be set to point to the root directory of the Schmant installation that Hudson should use.

Project configuration

The following configuration properties can be set on a per-project basis:

Script file (required)

The path to the build script file. If this path is relative, it is interpreted relative to the build workspace root directory.

Variables

Variables (key=value) that are available to the build script in the props variable.

Script arguments

Arguments that are available to the build script in the args variable.

System properties

Additional system properties to set. System properties are available to the build script in the props variable.

Verbosity

Determines the verbosity of Schmant. Any verbosity level above INFO will generate a lot of output.

Task package path

The path to additional Schmant task packages. Path entries are separated by the host operating system's path separator char (':' on Unix, ';' on Windows).

Script engine name

The name of the script engine to use for running the build script. If this is not set, the script engine will be inferred from the build script's file name extension.

Additional classpath

Additional Jar files to add to Schmant's classpath. This can be used to add Jar files for the script engine to use if they are not installed in the JDK.

Changelog

Version 1.1.4 (2009/12/15)

• The plugin now launches Schmant in a separate process. This plugs a few memory leaks.

Version 1.0 (2009/04/01)

• Initial version