phpUnderControl

Info | HTML | Text

Frequently asked questions and Troubleshooting

Invalid File or Directory artifacts/BankAccount/.../coverage/index.html

If you get this or a similar error message, then your CruiseControl installation contains a directory named artifacts. If this directory exists, CruiseControl will always look for project artifacts in this directory. Simply change the artifactpublisher-tags in your config.xml from logs/${project.name} to artifacts/${project.name}. Now CruiseControl will move the generated contents into the expected directory.

I updated phpUnderControl, but I still get no shiny Metric-Charts

You have updated phpUnderControl, but you still get the old metric charts. You must adjust the publishers-section of the config.xml for your existing projects to get new shiny charts, generated by phpUnderControl, from this.

<publishers> <execute command="phpuc graph logs/${project.name}"/> </publishers>

If you use the artifacts folder for output you must add a second argument to the graph command.

<publishers> <execute command="phpuc graph logs/${project.name} artifacts/${project.name}" /> </publishers>

This example is based on the PEAR installer and expects that phpuc is in the PATH environment variable. If you use the svn checkout, please change phpuc to phpuc.php.

No tag "jmxbase" defined in tag library imported with prefix "cruisecontrol"

When you try to open the phpUnderControl dashboard and get this error message, then the used CruiseControl version is to old. The referenced tutorial mentions the version 2.4.1 that was ok and up to date in 2006, but please update your CruiseControl installation to a more recent version.

I get an error about an invalid checkstyle.xml document

This could happen if you don't specify the optional @error attribute for the ant exec task. If this attribute is not specified every output, including all errors and warning, is logged into the checkstyle.xml document.

Are there any example configurations for phpUnderControl?

Yes, phpUnderControl provides two full documented build.xml and config.xml files that can be found in the docs directory.

Revision 5
By Manuel Pichler
At Sat, 26 Apr 2008 16:41:55 +0200