This plugin allows you to use Phing to build PHP projects.
If you have multiple Phing installations, you can configure Jenkins to allow that each project will select the installation that will use.
If phing is in the path, you don't have to configure phing.
You can use environment variables in PHING_HOME like $WORKSPACE, $HOME etc.
For composer users, if you have phing installed in $HOME/vendor/bin/phing, then specify ''$HOME/vendor/'' or ''$HOME/vendor/bin'' as PHING_HOME.
For PEAR users, if you have phing installed in /usr/bin/phing, then specify ''/usr'' or ''/usr/bin'' as PHING_HOME.
Do not specify "Subdirectory of extracted archive".
This plugin works as other builders like Ant builder or Gant builder.
- sone fixes.
- Windows phing is broken, jenkins tries to execute phing.bat with php.exe (JENKINS-17668).
- Support Phing auto installer.
- added Options field to specify logger (JENKINS-17073).
- Allow environment variables in phing properties (JENKINS-16967).
- Specifying custom phing build file does not work (JENKINS-12995).
- Fixed that 'Use ModuleRoot as working directory' checkbox is not checked correctly.
- added "Use ModuleRoot as working dire 'Use ModuleRoot as working directory' checkbox is not checked correctly. ctory" checkbox on project configuration page. (JENKINS-12078)
- Fixed the description of Phing on system configuration page.
- Support Environment variables in the "Build file" field such as "$WORKSPACE/build.xml". (JENKINS-8549)
- Fixed Information of certain Phing tasks does not display in console output of the build. (JENKINS-8097)
- Supported ConsoleNoteAnnotator.
- Added "Executed Phing Target".
- Fixed NotSerializableException using Phing plugin with slaves. Thanks mdillon. (JENKINS-6615)
- Fixed JENKINS-4398.
- Fixed deprecated api.
- Fixed JENKINS-2504.
- Fixed NPE when no targets are specified.
- First Version