When using an environment variable to give a more specific location of a Phing build file, such as $BRANCH_DIR, the plugin is not parsing the environment variable. Because of this, it attempts to load the literal "$BRANCH_DIR/build.xml" and append it onto the workspace path. This is not the expected behavior since using the exact same method with the Ant task does parse and expand the variable correctly.

Example input on job configuration:

Invoke Phing targets
– Targets: stage deploy
– Phing Build File: $WORKSPACE/build.xml

Example output when built:

[$WORKSPACE] $ phing -buildfile build.xml stage deploy -logger phing.listener.DefaultLogger
FATAL: command execution failed.Maybe you need to configure the job to choose one of your Phing installations?
java.io.IOException: Cannot run program "phing" (in directory "/usr/local/hudson/workspace/job_1/$WORKSPACE"): java.io.IOException: error=2, No such file or directory