* add the jstest target to the live build.xml
* add php file audit to jenkins build
* customized version of audit_js_unit_test_coverage.py to work with
  the phantomjs layout, and include it in build.xml
* have the coverage script be a bit more verbose in the jenkins invocation, and actually execute that target from build.xml
* typo
* actually cast the list variable to a string
* add cobertura plugin to jenkins and process the JSCover cobertura
  coverage report as part of the default config for a buttonmen project
Merge pull request #449 from cgolubi1/419_jenkins_js

finish adding javascript testing and custom file audits to jenkins