[
https://issues.jenkins-ci.org/browse/JENKINS-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-12995.
--------------------------------------------
Resolution: Fixed
> Specifying custom phing build file does not work
> ------------------------------------------------
>
> Key: JENKINS-12995
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12995
> Project: Jenkins
> Issue Type: Bug
> Components: phing
> Affects Versions: current
> Environment: root@jenkins:~# lsb_release -a
> Distributor ID: Ubuntu
> Description: Ubuntu 10.04.3 LTS
> Release: 10.04
> Codename: lucid
> Reporter: Daniel Sloof
> Assignee: sogabe
> Labels: jenkins, plugin
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
