Jenkins git ignore
# Only get the config.xml from any Jobs directory
# Process jobs that exist in folders
# More files
# Contains local info and secrets; don’t want this in Git
Back to top
If you want to visualise PHPUnit code coverage then the Clover PHP will ingest a clover.xml file created by PHPUnit and create a graph on the job home page. You can also use it to ensure a minimum amount of coverage or the project will be marked as unstable or even fail the build.
Other plugins that create graphs and logs from PHPUnit and other QA tools include:
Checkstyle (for processing PHP_CodeSniffer logfiles in Checkstyle format)
Crap4J (for processing PHPUnit's Crap4J XML logfile)
DRY (for processing phpcpd logfiles in PMD-CPD format)
JDepend (for processing PHP_Depend logfiles in JDepend format)
Plot (for processing phploc CSV output)
PMD (for processing PHPMD logfiles in PMD format)
xUnit (for processing PHPUnit's JUnit XML logfile)
The HTML Publisher allows you to keep HTML reports generated by your tests and link to them from a job page.
The AnsiColor plugin adds support for ANSI escape sequences, including color, to the build output.
You can report build statuses back to Hipchat, Slack and IRC with respective plugins.
This plugin allows you to run tasks like shell scripts after builds finish - I use it to stop Docker containers that I've used in my builds.
The S3 publisher plugin will create an archive from a successful build and push it to Jenkins (which you could then automatically pull on to you servers to deploy new code).
One of my favourite plugins is the Big Monitor plugin which I have running on a TV (projected from a spare Mac Mini using a Chromecast). This is opposite my desk in the office and I can see all of my jobs and their current status (which of course are always green...).