Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: phing-plugin
-
Environment:root@jenkins:~# lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid
-
Similar Issues:
Description
Since the release of version 0.10, which properly fixes the issue in specifying that moduleroot should be default directory, I can no longer specify a custom phing build file path.
looking for '/var/lib/jenkins/jobs/[SOME_JOB]/workspace/Build/Scripts/build.xml' ...
[workspace] $ phing -buildfile build.xml build-all deploy [SOME_PROPERTIES_WERE_OMITTED]
Buildfile: build.xml does not exist!
This absolute path does actually exist, and 'Phing Build File' path is simply 'Build/Scripts/build.xml'. So it looks like it is looking for the file in the right location, but then reverts to using just the filename when executing phing.
Code changed in jenkins
User: Seiji Sogabe
Path:
src/main/java/hudson/plugins/phing/PhingBuilder.java
src/main/resources/hudson/plugins/phing/Messages.properties
src/main/resources/hudson/plugins/phing/Messages_ja.properties
src/main/resources/hudson/plugins/phing/PhingBuilder/config.jelly
http://jenkins-ci.org/commit/phing-plugin/3ec6a9bdd797a4f2f2decc932c2ea0d91eb0e631
Log:
[FIXED JENKINS-12995] specify absolute path of build script.