First off, Travis CI is only usable through github. It’s a great service that allows tests to be run before pull requests are merged, helping to ensure code stability. It’s a very new service, and PHP support is in flux. Almost daily information changes. So I fear this will be outdated tomorrow. Regardless, I wanted to get this written down.<\/p>\n
The magic all happens in the .travis.yml file. It’s a config file that tells travis what to run. It only has a few sections, but they can be tricky. Here is the example .travis.yml for PHP:<\/p>\n
\r\nlanguage: php\r\n\r\n# list any PHP version you want to test against\r\nphp:\r\n # using major version aliases\r\n\r\n # aliased to 5.2.17\r\n - 5.2\r\n # aliased to a recent 5.3.x version\r\n - 5.3\r\n # aliased to a recent 5.4.x version\r\n - 5.4\r\n\r\n# optionally specify a list of environments, for example to test different RDBMS\r\nenv:\r\n - DB=mysql\r\n - DB=pgsql\r\n\r\n# execute any number of scripts before the test run, custom env's are available as variables\r\nbefore_script:\r\n - if [[ "$DB" == "pgsql" ]]; then psql -c "DROP DATABASE IF EXISTS hello_world_test;" -U postgres; fi\r\n - if [[ "$DB" == "pgsql" ]]; then psql -c "create database hello_world_test;" -U postgres; fi\r\n - if [[ "$DB" == "mysql" ]]; then mysql -e "create database IF NOT EXISTS hello_world_test;" -uroot; fi\r\n\r\n# omitting "script:" will default to phpunit\r\n# use the $DB env variable to determine the phpunit.xml to use\r\nscript: phpunit --configuration phpunit_$DB.xml --coverage-text\r\n\r\n# configure notifications (email, IRC, campfire etc)\r\nnotifications:\r\n irc: "irc.freenode.org#travis"\r\n<\/pre>\nNot included libs<\/strong><\/p>\n
Currently this will not work. Their phpunit is requiring libraries that aren’t included in the vm that’s created. Regardless of if your project is using these libraries:<\/p>\n
\r\nbefore_script:\r\n # everything after this point is needed to just use phpunit\r\n - pear channel-discover pear.phpunit.de\r\n - pear install phpunit\/PHP_Invoker\r\n - pear install phpunit\/DbUnit\r\n - pear install phpunit\/PHPUnit_Selenium\r\n - pear install phpunit\/PHPUnit_Story\r\n<\/pre>\nDatabase usage<\/strong><\/p>\n
I use mysql currently. The problem I hit was you can create users, but you can’t grant them privilages. So you HAVE to use the default root user with no password.<\/p>\n
\r\nenv:\r\n - DB=mysql\r\n\r\n# execute any number of scripts before the test run, custom env's are available as variables\r\nbefore_script:\r\n - mysql -e 'CREATE DATABASE `quizmo_dev`;'\r\n # The following is fine, but travis won't allow granting privilages\r\n # - mysql -e "CREATE USER 'quizmo_dev'@'localhost' IDENTIFIED BY 'quizmo_dev';"\r\n # - mysql -e "GRANT ALL PRIVILEGES ON *.* TO 'quizmo_dev'@'localhost' WITH GRANT OPTION;"\r\n # migrating adds all tables\r\n - quizmo\/protected\/yiic migrate --interactive=0\r\n<\/pre>\nNotifications don’t work<\/strong><\/p>\n
I’m assuming this is something they’ll fix soon. I’m just trying to use email notifications — but it never sends an email.<\/p>\n","protected":false},"excerpt":{"rendered":"
First off, Travis CI is only usable through github. It’s a great service that allows tests to be run before pull requests are merged, helping to ensure code stability. It’s a very new service, and PHP support is in flux. Almost daily information changes. So I fear this will be outdated tomorrow. Regardless, I wanted […]<\/p>\n","protected":false},"author":4571,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[910,64019,3163],"tags":[64049,64050],"class_list":["post-462","post","type-post","status-publish","format-standard","hentry","category-development","category-open-source-development","category-php","tag-continuous-integration","tag-travis-ci"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/users\/4571"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/comments?post=462"}],"version-history":[{"count":8,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/462\/revisions"}],"predecessor-version":[{"id":475,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/462\/revisions\/475"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/media?parent=462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/categories?post=462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/tags?post=462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}