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™.

Executable Command

Executable projects define a single recipe which executes a single executable command.

The executable to run 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.

Running Scripts On some platforms, to run a shell script you will need to specify the shell binary as the exe for your executable command, and the script itself as an argument to that command (perhaps after a shell-specific flag).

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 project.