For quite some time we run the unit tests for our libs and tools against PHP and HHVM, at least that is what I thought up to now. As it turns out I missed a minor detail. In our Jenkins job we invoke the Phing task like this:
Before anybody complains: I know that "as of 2014-10-21 PSR-0 has been marked as deprecated. PSR-4 is now recommended as an alternative." - Anyway I still think this little gem makes sense to be shared because a lot of people are probably not aware of it. I recently found out by accident that it is possible pass a task name in PSR-0 style to the "taskdef" task. In the old days you had to use the Java-like dot-style notation like this and also define the classpath to make sure the class could be loaded correctly:
About a year and a half ago Fabien Potencier announced the PHP Security Advisories Database initiative. Part of the initiative the SensioLabs Security Advisories Checker (beta) website came to life. The website and the api behind it makes it very easy to check your composer.lock file for dependencies which "have issues". Either upload your composer.lock file to the website or use the CLI tool to communicate with the api directly. About 2 weeks ago Fabien took the next step forward and announced that the Security Advisories Database is distributed as public domain and as such can now be "controlled" by the community.
Recently I needed to run a script on server via SSH. To automate things I wanted to execute the script via Phing. The command I wanted to execute looked like this:
Vom 24.02.2014 bis zum 28.02.2014 findet in Montreal die ConFoo 2014 Konferenz statt. Ich bin dieses Mal wieder dabei und kann zwei neue Vorträge präsentieren: Im Vortrag "The seven deadly sins of Dependency Injection" möchte ich darstellen welche Fehler man bei der Verwendung des Dependency Injection Patterns nicht machen sollte. Der Vortrag "The Setup: Composer, Phing, Vagrant, Jenkins" beleuchtet unsere Arbeitsweise mit den genannten Tools soll aufzeigen wie man mit den Tools arbeiten kann (aber nicht muss).
Vom 25.02.2013 bis zum 01.03.2013 findet in Montreal die ConFoo Conference 2013 statt. Ich freue mich als Sprecher eingeladen zu sein und werde die Vorträge "Testing untestable code", "Offline strategies for HTML5 web applications" und "A Phing fairy tale" präsentieren.
Nils Langner lädt ein und ich komme: Gemeinsam mit Lars Jankowsky, Johann-Peter Hartmann, Bastian Feder, Björn Kaiser und Simon Hohenadl gestalten wir einen Track bei der Web Developer Conference 2012 die vom 17.09.2012 - 18.09.2012 in Hamburg statt findet. Ich werde den Vortrag "Große Systeme, lose Kopplung, Spaß bei der Arbeit!" präsentieren und skizzieren wie man es schafft Komponenten zu entkoppeln um die Wartbarkeit zu vereinfachen.
Zum heutigen Tage wurde die Version 2.4.0 von Phing freigeben und es freut uns, dass unsere Liquibase Extension endlich auch in der offiziellen Phing Distribution angekommen ist.
As stated last year, our Liquibase Extension for Phing got merged in the master development branch by the help of Michiel Rook. Next steps will be to provide a decent kind of documentation as well as some already planned optimizations. If everything works out fine, you should be able to use Liquibase soonish from Phing without any work-a-rounds. As always we are looking for pointers for improvement and general feedback. In a soon to follow blog post I`ll try to describe how we use Liquibase in one of your projects.
I am happy to announce that bitExpert will contribute the Liquibase Phing codebase to the Phing project. The transition phase will start pretty soon. Unfortunately this means that the source code will no longer be maintained on github, instead the Phing subversion repository will be the new home for the extension.