Phing is a PHP project build system or build tool based on Apache Ant. You can do anything with it that you could do with a traditional build system like GNU make, and its use of simple XML build files and extensible PHP "task" classes make it an easy-to-use and highly flexible build framework.
Features include running PHPUnit unit tests (including test result and coverage reports), file transformations (e.g. token replacement, XSLT transformation, template transformations), file system operations, interactive build support, SQL execution, Git, Mercurial and Subversion operations, tools for creating PEAR packages, documentation generation (PhpDocumentor, ApiGen) and much, much more.
If you find yourself writing custom scripts to handle the packaging, deploying, or testing of your applications, then we suggest looking at Phing. Pre-packaged with numerous out-of-the-box operation modules (tasks), and an easy-to-use OO model to extend or add your own custom tasks.
Install Phing by adding a dependency to phing/phing to the require-dev or require section of your project's composer.json configuration file, and running 'composer install':
{ "require-dev": { "phing/phing": "2.*" } }
Or, if you want to install the latest alpha version:
{ "require-dev": { "phing/phing": "3.*" }, "minimum-stability": "alpha" }
Download the Phar archive (version 3.0.0, sha-512 hash). The archive can then be executed by running:
php phing-latest.phar
Or directly download a specific version:
NB: starting from 3.0.0, all releases are signed using GPG. The [email protected] public key can be downloaded here. To verify a release, run:
curl https://keys.openpgp.org/vks/v1/by-fingerprint/56697956EBD451594B03AEFDD5F0CB76E2DD74F8 | gpg --import gpg --verify phing-3.0.0.phar.asc
Our PEAR channel has been deprecated. Phing is only available through Composer or as a .phar archive.
Phing is only available through Composer or as a .phar archive.
The most comprehensive source for Phing documentation.
NB: the documentation links below are autogenerated from the latest Phing development version. For the latest stable version, please refer to this repository.
More Phing (related) presentations can be found here: https://www.slideshare.net/tag/phing
We contributions! There are a number of ways that you can get involved in Phing development.
We greatly appreciate it when users report issues or come up with feature requests. However, there are a few guidelines you should observe before submitting a new issue:
Issues can be reported on GitHub.
We can always use better documentation. The user guide is written in DocBook and can be found in docs/guide/en/source. The source is rendered to multiple formats (html, pdf, etc.), these can be found in docs/guide/en/output).
Developing and maintaining Phing has cost many hours over the years. If you want to show your appreciation, you can use one of the following methods to donate something to the project maintainer, Michiel Rook:
Thank you!
To successfully run all Phing tests, please ensure you have the following setup:
Then, perform the following steps (on a clone/fork of Phing):
composer install cd test ../bin/phing
The best way to submit code to Phing is to make a Pull Request on GitHub. Please help us merge your contribution quickly and keep your pull requests clean and concise: squash commits and don't introduce unnecessary (whitespace) changes. Phing's source code is formatted according to the PSR-2 standard.
Phing's source code is hosted on GitHub.
There are several ways to get help if you are having problems with Phing.