Overview

Executables projects can be used to run any build that consists of a single command. Typical examples are builds run from a custom script, or via builds tools that are not directly supported in pulse™.

Configuration

executable

The executable to run. This should be specified as either a command in the PATH or the absolute path of the file to execute. If the file to execute is within your source tree, use ${base.dir} to construct the absolute path. This property refers to the base directory for the build, where your source code is checked out.

This setting is required.

Platform Independence Some build commands may have different names on different platforms. To make your configuration platform independent, you will need to parameterise the exact value of this setting. This can be achieved by setting the value to a property reference, and by using resources to introduce different values for the property on different agents. For example, set the value to ${buildtool.bin}, then add this property to a resource named "buildtool" on each agent, and import the resource in the build specification.

Examples

Run the script scripts/my-build.sh in your source tree:

${base.dir}/scripts/my-build.sh

Run the command buildtool which is in the PATH:

buildtool

arguments

A space-separated list of command line arguments to pass to to the executable.

This setting is not required.

working directory

If you wish to execute the command from a specific directory, provide the path of the directory, relative to the base directory for the recipe.

This setting is not required. By default, the command will be executed in the base directory for the build.