{"issue":{"created_at":"2011-11-17T15:52:44Z","state":"closed","updated_at":"2011-11-21T08:08:01Z","user":{"gravatar_id":"5c299a02c11ce797f20df385f560a16a","id":77759,"url":"https://api.github.com/users/pborreli","login":"pborreli","avatar_url":"https://secure.gravatar.com/avatar/5c299a02c11ce797f20df385f560a16a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":13,"body":"Travis CI is an open, distributed build system for the open source community.\r\n\r\nHere the blog post for the PHP support announcement : http://about.travis-ci.org/blog/first_class_php_support_on_travis_ci/\r\n\r\nEach commit in the repo will trigger travis-ci.org hook and will launch phpunit against multiple version of PHP (5.3.8, 5.4.0RC1 and soon 5.3.2, 5.3-snapshot and 5.4-snapshot)\r\n\r\nFor now we noticed almost no false-positive or downtime.\r\n\r\nAn icon to show the status of the repo (or a specific build) is included in my PR (change pborreli by symfony).\r\n\r\nhttp://about.travis-ci.org/docs/user/languages/php/\r\n\r\nThis doesn't replace our jenkins platform in any case. it's another way to bulletproof our code and a great way for a contributor to check his Symfony fork before to submit any PR, like that : \r\n\r\n[![Build Status](https://secure.travis-ci.org/pborreli/symfony.png?branch=travis)](http://travis-ci.org/pborreli/symfony)","assignee":null,"id":2270142,"pull_request":{"patch_url":"https://github.com/symfony/symfony/pull/2664.patch","html_url":"https://github.com/symfony/symfony/pull/2664","diff_url":"https://github.com/symfony/symfony/pull/2664.diff"},"number":2664,"labels":[],"title":"travis-ci.org integration","closed_at":"2011-11-17T16:02:29Z","html_url":"https://github.com/symfony/symfony/issues/2664","milestone":null,"url":"https://api.github.com/repos/symfony/symfony/issues/2664"},"action":"created","comment":{"created_at":"2011-11-21T08:08:01Z","updated_at":"2011-11-21T08:08:01Z","user":{"gravatar_id":"54787afbd0e7c30936101c2fa84bd89b","id":300279,"url":"https://api.github.com/users/lsmith77","login":"lsmith77","avatar_url":"https://secure.gravatar.com/avatar/54787afbd0e7c30936101c2fa84bd89b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"did you read up on what travis actually offers? did you read my RFC on the mailinglist?\r\n\r\nif did you would realize that your answer misses the point entirely. \r\n\r\nit would be like me saying big -1 for jenkins since we do not test feature branches and PRs.\r\n\r\nagain the topic isnt if travis replaces jenkins, the two are simply complementary services and travis requires the addition of a single file in order to do its magic. thats it.\r\n\r\nOn 21.11.2011, at 08:56, Hugo Hamon <reply@reply.github.com> wrote:\r\n\r\n> Travis CI only runs the tests suite if I'm not mistaking so it's a big -1 for me against Jenkins.\r\n> \r\n> With Jenkins we can other analysis tools like PMD, PDepend, Docblox, PHPLOC, PHPCPD...\r\n> \r\n> --- \r\n> Reply to this email directly or view it on GitHub:\r\n> https://github.com/symfony/symfony/pull/2664#issuecomment-2812352","id":2812412,"url":"https://api.github.com/repos/symfony/symfony/issues/comments/2812412"}}