Docker image with Jenkins CI and full PHP configuration and tools

See it in action here.

Get the source from Github here.

This Docker image follows the configuration for installing Jenkins CI and the PHP testing tools.

It uses Ubuntu 14.04 LTS image.

The PHP 5.5 PPA by Ondřej Surý is used for the latest version of PHP and its extensions.

For Jenkins the Debian deb repo is used.

The deb is used for faster local updating/downloading of the apt packages.

DEBIAN_FRONTEND=noninteractive and apt-get -qq are used for automatic silent installs.

date.timezone=Europe/Sofia and ;disable_functions= are set in php.ini

After Jenkins is installed and needs its first update there is a wait of 60 seconds until the update script is called.

The Jenkins server is first updated before installing the plugins.

Currently these plugins are installed: checkstyle cloverphp crap4j dry htmlpublisher jdepend plot pmd violations xunit.

And these PHP testing tools are installed globally through Composer: phpunit/phpunit, squizlabs/php_codesniffer, phploc/phploc, pdepend/pdepend, phpmd/phpmd, sebastian/phpcpd, theseer/phpdox.

Composer installs the tools in /home/jenkins/.composer and makes all of them available globally in /usr/local/bin/.

Composer is set to use git to fetch the dependencies to avoid the GitHub API rate limits.

Port 8080 is exposed and available. This is the default Jenkins’ port.

The default CMD in the image is: “sh /”


First download the image:

docker pull iliyan/jenkins-ci-php:1.0.0

And run it:


docker run -d --name jenkins -p localhost:8080:8080 iliyan/jenkins-ci-php:1.0.0

Visible from outside on a hosting server:

docker run -d --name jenkins -p VISIBLESERVERPORT:8080 iliyan/jenkins-ci-php:1.0.0

Alternative usage of the PHP testing tools:

You can download all of the tools from your project’s composer.json file adding them for example in the dev secion like I did here and here.

How to Read and Improve the C.R.A.P Index of your code |

I’ve been looking at the CRAP index on my jenkins php configuration inside the Crap4J pages and found this blog post to be helpful about what CRAP is and how to deal with it (use it to your advantage).

How to Read and Improve the C.R.A.P Index of your code |

Creating your first Composer/Packagist package – Junior Grossi

I am going to create my first Packagist package and found this tutorials useful:

Creating your first Composer/Packagist package – Junior Grossi.


as well as:

PHPStorm 8 is out!

You can check the latest changes here:

I really like these things: PHP 5.6, PSR-4, Behat and AngularJS are supported, there is a new JavaScript and Node.js tracing tool called Spy-js, Multiple Carets and Selections is a neat feature that I think I’ve seen in SublimeText only so far, Work with individual files without creating a project – I need that from time to time, and so on..

As a whole this is a big update that makes the software even more powerful and the only one you need for development.

Just started learning PhalconPHP

I just started learning it by reading its online documentation. I will definitely have to find a book about it and there is at least one out there and also I have to pass through all the examples like 10 times until I sit and make something with it. The installation of course is the easiest part, even inside a Vagrant box or Docker.