phing

I am using a Phing build script with Jenkins and would like to run it end to end on a job and capture all the reports. The problem is it stop building on a failed build step. Is there a way or a plugin that would continue the job even on failures? Thanks I don't know a lot about Phing but, since it's based on Ant, if the build step you are executing has a "failonerror" attribute you should be able to set it to false so that the entire build doesn't fail if the step returns an error. Yes, use try, catch block in you pipeline scripts example: try { // do some stuff that potentially fails } catch

Max OS X 10.7.. when i run phing -v i get the following errors: Warning: require_once(phing/Project.php): failed to open stream: No such file or directory in /usr/lib/php/pear/phing/Phing.php on line 22 Fatal error: require_once(): Failed opening required 'phing/Project.php' (include_path='.:') in /usr/lib/php/pear/phing/Phing.php on line 22 Here are the commands i used: pear config-set auto_discover 1 pear install phing/phing Here is my php.ini: include_path = ".:/Applications/MAMP/bin/php/php5.3.6/lib/php" running whereis for php, pear, and phing returns: bash-3.2$ whereis php /usr/bin/php

I'm having problems running phpunit under MAMP on OS X 10.6. I've installed phpunit via PEAR and it is exists in the MAMP directory but when I run phpunit in terminal nothing happens. I'm guessing that this is a path problem but as a os x newbie, I don't know how to fix it. This is what happens when I try to run it from /Applications/MAMP/bin/php5.3/bin $ phpunit -bash: /usr/bin/phpunit: No such file or directory $ ./phpunit $ The problem looks very similar to this How to Install phpunit 3.5 on mac with MAMP but the solutions there haven't worked so far. Here is some more system info: Location

I want to create phing task for some plugins so the directory structure is something like root - plugin1 - index.php - plugin2 - index.php etc.. I want to run same tasks on each subdirectory - for example generate doc for plugin1 run unit tests for plugin1 deploy plugin1 somewhere generate doc for plugnin2 ... Is this possible? I need something like <foreach param="filename" absparam="absfilename" target="subtask"> <fileset dir="."> <include name="*.php"/> </fileset> </foreach> but for directories. Or do I have to write build.xml for each plugin standalone? Thanks a lot. Finally I discovered

Does anyone use Phing to deploy PHP applications, and if so how do you use it? We currently have a hand-written "setup" script that we run whenever we deploy a new instance of our project. We just check out from SVN and run it. It sets some basic configuration variables, installs or reloads the database, and generates a v-host for the site instance. I have often thought that maybe we should be using Phing . I haven't used ant much, so I don't have a real sense of what Phing is supposed to do other than script the copying of files from one place to another much as our setup script does. What

I'm using Phing to do post build tasks in Hudson. I want to generate changelog containing all commits since last successful Hudson build. But looks like neither Hudson nor Git plugin for Hudson does not provide %last_build_time% variable. This would be satisfying solution, (but how to get the time?): git log --pretty="%s" --since="%last_build_time%" The only way I see for now is extracting it from the job xml file, but I do not know if it is possible with Phing. How do you generate your change logs? @takeshin's answer is fine if you have access to the build.xml file, but this may break,

How to correctly deploy applications from development to production and how to deal with multiple site configurations. All my development are done thru svn located at var/svn/myapp/trunk and the actual production code is in /var/www/myapp. I check out the latest code to my local machine into a directory called "myapp_latest_svn". I have site and location specific code in my main settings.php, which has H_PATH = ' http://myapp.com ' & db config settings for db_host, db_user_name and db_password which is as you know different in local machine settings ( where localhost/myapp.com is just an