Permalink
Browse files

add till to the php announcement

  • Loading branch information...
Sven Fuchs
Sven Fuchs committed Nov 13, 2011
1 parent e6e8774 commit 0735f8bceeba9f9fed56a6487ed0a9af3436f642
Showing with 211 additions and 194 deletions.
  1. +1 −1 2011/welcome-to-travis/index.html
  2. +26 −22 blog.xml
  3. +9 −9 blog/big_refactoring/index.html
  4. +5 −5 blog/first_class_nodejs_support_on_travis_ci/index.html
  5. +9 −5 blog/first_class_php_support_on_travis_ci/index.html
  6. +13 −13 blog/hello_world/index.html
  7. +20 −16 blog/index.html
  8. +1 −1 blog/vm_upgrade_nov_11_2011/index.html
  9. +1 −1 blog/vm_upgrade_oct_31_2011/index.html
  10. +4 −4 docs/dev/build_tasks/index.html
  11. +12 −12 docs/dev/worker/index.html
  12. +5 −5 docs/user/build-configuration/index.html
  13. +2 −2 docs/user/ci-environment/index.html
  14. +7 −7 docs/user/database-setup/index.html
  15. +5 −5 docs/user/getting-started/index.html
  16. +1 −1 docs/user/how-to-skip-a-build/index.html
  17. +4 −4 docs/user/languages/clojure/index.html
  18. +2 −2 docs/user/languages/erlang/index.html
  19. +1 −1 docs/user/languages/index.html
  20. +2 −2 docs/user/languages/javascript-with-nodejs/index.html
  21. +3 −3 docs/user/languages/php/index.html
  22. +4 −4 docs/user/languages/ruby/index.html
  23. +2 −2 docs/user/selenium-setup/index.html
  24. +3 −3 docs/user/status-images/index.html
  25. +2 −2 fr/2011/welcome-to-travis/index.html
  26. +12 −12 fr/docs/dev/worker/index.html
  27. +16 −16 fr/docs/user/build-configuration/index.html
  28. +2 −2 fr/docs/user/ci-environment/index.html
  29. +7 −7 fr/docs/user/database-setup/index.html
  30. +6 −6 fr/docs/user/getting-started/index.html
  31. +2 −2 fr/docs/user/how-to-skip-a-build/index.html
  32. +1 −1 fr/docs/user/languages/clojure/index.html
  33. +2 −2 fr/docs/user/languages/erlang/index.html
  34. +1 −1 fr/docs/user/languages/index.html
  35. +1 −1 fr/docs/user/languages/javascript-with-nodejs/index.html
  36. +3 −3 fr/docs/user/status-images/index.html
  37. +2 −2 fr/index.html
  38. +2 −2 index.html
  39. +10 −5 source/content/blog/first_class_php_support_on_travis_ci.md
@@ -45,7 +45,7 @@ <h2>Welcome to Travis CI</h2>
<p>Travis CI is an open-source, distributed build system for the open source community.</p>
-<p>We are going to blog more about it later but for now you can read up on the <em>initial ideas</em> on <a href="http://svenfuchs.com/2011/2/5/travis-a-distributed-build-server-tool-for-the-ruby-community">Sven&rsquo;s blog</a> and flip through <a href="http://talk-2011-lyon.heroku.com">a presentation</a> that we gave at 3 conferences and 2 Ruby user groups this summer.</p>
+<p>We are going to blog more about it later but for now you can read up on the <em>initial ideas</em> on <a href="http://svenfuchs.com/2011/2/5/travis-a-distributed-build-server-tool-for-the-ruby-community">Svens blog</a> and flip through <a href="http://talk-2011-lyon.heroku.com">a presentation</a> that we gave at 3 conferences and 2 Ruby user groups this summer.</p>
<p>If you feel like this is a great project then jump into <a href="irc://travis#irc.freenode.net">#travis on irc.freenode.net</a> and say hi!</p>
View
@@ -15,7 +15,7 @@
<published>2011-11-13T16:08:00Z</published>
<updated>2011-11-13T16:08:00Z</updated>
<link rel="alternate" href="http://about.travis-ci.org//blog/first_class_php_support_on_travis_ci/"/>
- <content type="html">&lt;p&gt;Today we are happy to announce first class PHP support with Travis CI. &lt;/p&gt;
+ <content type="html">&lt;p&gt;Today we are happy to announce first class PHP support with Travis CI.&lt;/p&gt;
&lt;p&gt;It includes all the same features Ruby, Erlang and Node.js projects enjoy today, including:&lt;/p&gt;
@@ -28,11 +28,12 @@
&lt;/ul&gt;
&lt;p&gt;Over the last several weeks many nice folks from the PHP community have been working with the Travis team
-and it would not be possible without all the help from &lt;a href="https://twitter.com/loicfrering"&gt;Lo&#239;c Frering&lt;/a&gt; and &lt;a href="https://github.com/pborreli"&gt;Pascal Borreli&lt;/a&gt;. &lt;a href="https://twitter.com/old_sound"&gt;&#193;lvaro Videla&lt;/a&gt; and
-&lt;a href="https://github.com/lsmith77"&gt;Lukas Kahwe Smith&lt;/a&gt; helped us with testing by adding some of the &lt;a href="https://github.com/friendsofsymfony"&gt;Friends of Symfony&lt;/a&gt; projects on Travis early on.
+and it would not be possible without all the help from &lt;a href="https://twitter.com/loicfrering"&gt;Loïc Frering&lt;/a&gt; and &lt;a href="https://github.com/pborreli"&gt;Pascal Borreli&lt;/a&gt;. &lt;a href="https://github.com/till"&gt;Till Klampaeckel&lt;/a&gt; has helped us set up &lt;a href="http://sourceforge.net/p/phpfarm/wiki/Home/"&gt;phpfarm&lt;/a&gt; and &lt;a href="http://pear2.php.net/"&gt;pyrus&lt;/a&gt; and test drive the whole thing. &lt;a href="https://twitter.com/old_sound"&gt;Álvaro Videla&lt;/a&gt; and
+&lt;a href="https://github.com/lsmith77"&gt;Lukas Kahwe Smith&lt;/a&gt; also helped us a lot by running some of the &lt;a href="https://github.com/friendsofsymfony"&gt;Friends of Symfony&lt;/a&gt; projects on Travis early on.
Pascal also got Symfony, Twig, Silex, Doctrine and Monolog test suites up and running on travis-ci.org (we hope his patches will be accepted
-upstream). Having all those projects building fine for several days makes us confident that we are
-ready to ship this feature.&lt;/p&gt;
+upstream).&lt;/p&gt;
+
+&lt;p&gt;Having all those projects building fine for several days makes us confident that we are ready to ship this feature.&lt;/p&gt;
&lt;p&gt;Please see our &lt;a href="http://about.travis-ci.org/docs/user/languages/php"&gt;initial documentation for PHP projects&lt;/a&gt; and &lt;a href="http://about.travis-ci.org/docs/"&gt;the rest of the guides&lt;/a&gt;. We tried to link to as many real world .travis.yml examples to demonstrate all the features in action.&lt;/p&gt;
@@ -48,6 +49,9 @@ on.&lt;/p&gt;
&lt;h2 id="spread-the-word"&gt;Spread the word!&lt;/h2&gt;
&lt;p&gt;Feel free to &lt;a href="http://news.ycombinator.com/item?id=3231030"&gt;discuss and upvote on Hacker News&lt;/a&gt;&lt;/p&gt;
+
+&lt;p&gt;http://pear2.php.net/
+http://sourceforge.net/p/phpfarm/wiki/Home/&lt;/p&gt;
</content>
</entry>
<entry>
@@ -56,7 +60,7 @@ on.&lt;/p&gt;
<published>2011-11-11T06:18:00Z</published>
<updated>2011-11-11T06:18:00Z</updated>
<link rel="alternate" href="http://about.travis-ci.org//blog/vm_upgrade_nov_11_2011/"/>
- <content type="html">&lt;p&gt;travis-ci.org Ruby workers were upgraded, here is what&amp;rsquo;s new:&lt;/p&gt;
+ <content type="html">&lt;p&gt;travis-ci.org Ruby workers were upgraded, here is whats new:&lt;/p&gt;
&lt;h2 id="ruby-workers-changes"&gt;Ruby Workers Changes&lt;/h2&gt;
@@ -93,13 +97,13 @@ and watch our &lt;a href="https://github.com/travis-ci/travis-cookbooks/tree/mas
<content type="html">&lt;p&gt;One of the things people keep asking us is when language X will be a first class citizen on Travis-CI.
While it has been possible to build Node.js and C++ projects on Ruby workers for a while, it is not very convenient or intuitive, and such projects will not get the killer feature of travis-ci.org: testing against multiple versions/implementations. So we have good news for the Node.js community: Node.js is gaining first class support on Travis-CI, joining Ruby and Erlang.&lt;/p&gt;
-&lt;p&gt;Thanks to the hard work by &lt;a href="https://twitter.com/harrybrundage"&gt;Harry Brundage&lt;/a&gt; and the Travis core team, it is now possible to test your Node.js projects against multiple Node versions (currently 0.4.12, 0.5.8 and 0.6.0). We use &lt;a href="https://github.com/travis-ci/travis-cookbooks/blob/master/vagrant_base/nodejs/files/default/nvm.sh"&gt;NVM (&amp;ldquo;RVM for Node.js&amp;rdquo;) project&lt;/a&gt; and &lt;a href="https://github.com/travis-ci/travis-cookbooks/tree/master/vagrant_base/nodejs"&gt;Chef cookbooks&lt;/a&gt; to enable to easy switching of Node.js versions.&lt;/p&gt;
+&lt;p&gt;Thanks to the hard work by &lt;a href="https://twitter.com/harrybrundage"&gt;Harry Brundage&lt;/a&gt; and the Travis core team, it is now possible to test your Node.js projects against multiple Node versions (currently 0.4.12, 0.5.8 and 0.6.0). We use &lt;a href="https://github.com/travis-ci/travis-cookbooks/blob/master/vagrant_base/nodejs/files/default/nvm.sh"&gt;NVM (“RVM for Node.js”) project&lt;/a&gt; and &lt;a href="https://github.com/travis-ci/travis-cookbooks/tree/master/vagrant_base/nodejs"&gt;Chef cookbooks&lt;/a&gt; to enable to easy switching of Node.js versions.&lt;/p&gt;
&lt;p&gt;In addition, Shopify now sponsors a machine that we will be running five Node.js workers on. Please thank them by sending a loving tweet or two to &lt;a href="https://twitter.com/shopify"&gt;@Shopify&lt;/a&gt; :)&lt;/p&gt;
&lt;h3 id="how-do-i-test-my-project-against-multiple-nodejs-versions"&gt;How do I test my project against multiple Node.js versions?&lt;/h3&gt;
-&lt;p&gt;To test your Node.js project against multiple Node versions, add a &amp;lsquo;.travis.yml&amp;rsquo; file to your GitHub repository and add the following to it:&lt;/p&gt;
+&lt;p&gt;To test your Node.js project against multiple Node versions, add a .travis.yml file to your GitHub repository and add the following to it:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;language: "node_js"
node_js:
@@ -108,14 +112,14 @@ node_js:
- 0.6
&lt;/code&gt;&lt;/pre&gt;
-&lt;p&gt;When you define &amp;ldquo;node_js&amp;rdquo; as the language it tells Travis to switch the Node.js version (nvm use 0.4), install the dependencies of the project (npm install), and run the tests (npm test). If you define multiple Node.js versions to test against, like the above example, Travis will create a matrix of test configurations, in this case three builds will be queued. Or you can leave out the node_js versions to test against and Travis will use 0.4 by default. If your project is not yet Node 0.5 or 0.6 compatible,
+&lt;p&gt;When you define “node_js” as the language it tells Travis to switch the Node.js version (nvm use 0.4), install the dependencies of the project (npm install), and run the tests (npm test). If you define multiple Node.js versions to test against, like the above example, Travis will create a matrix of test configurations, in this case three builds will be queued. Or you can leave out the node_js versions to test against and Travis will use 0.4 by default. If your project is not yet Node 0.5 or 0.6 compatible,
you can exclude those versions. The same goes for project that want to only support 0.6, for example.&lt;/p&gt;
-&lt;p&gt;See Shopify&amp;rsquo;s &lt;a href="https://github.com/shopify/batman/blob/master/.travis.yml"&gt;Batman&lt;/a&gt; as well as &lt;a href="https://twitter.com/#!/martin_sunset"&gt;Martin Wawrusch&lt;/a&gt;&amp;rsquo;s &lt;a href="https://github.com/scottyapp/hook.io-blueprint-coffeescript/blob/master/.travis.yml"&gt;hook.io-blueprint-in-coffescript&lt;/a&gt; and &lt;a href="https://github.com/scottyapp/hook.io-amqp-listener/blob/master/.travis.yml"&gt;hook.io-amqp-listener&lt;/a&gt; projects as examples.&lt;/p&gt;
+&lt;p&gt;See Shopify’s &lt;a href="https://github.com/shopify/batman/blob/master/.travis.yml"&gt;Batman&lt;/a&gt; as well as &lt;a href="https://twitter.com/#!/martin_sunset"&gt;Martin Wawrusch&lt;/a&gt;’s &lt;a href="https://github.com/scottyapp/hook.io-blueprint-coffeescript/blob/master/.travis.yml"&gt;hook.io-blueprint-in-coffescript&lt;/a&gt; and &lt;a href="https://github.com/scottyapp/hook.io-amqp-listener/blob/master/.travis.yml"&gt;hook.io-amqp-listener&lt;/a&gt; projects as examples.&lt;/p&gt;
&lt;h2 id="the-workflow"&gt;The Workflow&lt;/h2&gt;
-&lt;p&gt;Travis&amp;rsquo; Node.js builder will do the following as part of the build process:&lt;/p&gt;
+&lt;p&gt;Travis Node.js builder will do the following as part of the build process:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Clone your repository from GitHub&lt;/li&gt;
@@ -150,7 +154,7 @@ you can exclude those versions. The same goes for project that want to only supp
</content>
</entry>
<entry>
- <id>tag:about.travis-ci.org,2011-11-01://blog/vm_upgrade_oct_31_2011/</id>
+ <id>tag:about.travis-ci.org,2011-10-31://blog/vm_upgrade_oct_31_2011/</id>
<title type="html">VM environment upgrade, Oct 31st, 2011</title>
<published>2011-10-31T20:26:26Z</published>
<updated>2011-10-31T20:26:26Z</updated>
@@ -182,7 +186,7 @@ against Rubinius in both modes, you can use the following list of Rubies in your
&lt;p&gt;Existing aliases for 1.8 mode (&lt;em&gt;rbx&lt;/em&gt; and &lt;em&gt;rbx-2.0&lt;/em&gt;) are still around and will work.&lt;/p&gt;
-&lt;p&gt;Rubinius&amp;rsquo; Ruby 1.9 features support is still a work in progress (it does not support encodings yet, for example) but
+&lt;p&gt;Rubinius Ruby 1.9 features support is still a work in progress (it does not support encodings yet, for example) but
we encourage Ruby developers to try testing their libraries against Rubinius, in both 1.8 and 1.9 modes. Now it is even
easier to do on travis-ci.org.&lt;/p&gt;
@@ -198,12 +202,12 @@ and watch our &lt;a href="https://github.com/travis-ci/travis-cookbooks/tree/mas
<published>2011-08-29T16:29:26Z</published>
<updated>2011-08-29T16:29:26Z</updated>
<link rel="alternate" href="http://about.travis-ci.org//blog/big_refactoring/"/>
- <content type="html">&lt;p&gt;We&amp;rsquo;ve just rolled out a big refactoring to the Travis CI &lt;a href="https://github.com/travis-ci/travis-ci"&gt;application&lt;/a&gt;
-(i.e. the server app which runs on Heroku) that we&amp;rsquo;ve been working on over the
+ <content type="html">&lt;p&gt;Weve just rolled out a big refactoring to the Travis CI &lt;a href="https://github.com/travis-ci/travis-ci"&gt;application&lt;/a&gt;
+(i.e. the server app which runs on Heroku) that weve been working on over the
last four weeks.&lt;/p&gt;
-&lt;p&gt;This refactoring was quite far-reaching and even though we&amp;rsquo;ve tried hard to
-make sure everything works fine there may be glitches and bugs that we&amp;rsquo;ve
+&lt;p&gt;This refactoring was quite far-reaching and even though weve tried hard to
+make sure everything works fine there may be glitches and bugs that weve
overlooked.&lt;/p&gt;
&lt;h2 id="why"&gt;Why?&lt;/h2&gt;
@@ -236,9 +240,9 @@ events and messages.&lt;/p&gt;
&lt;p&gt;You can find more information about the new domain model design &lt;a href="https://github.com/travis-ci/travis-ci/blob/statemachine_merge/docs/notes/build_tasks.md"&gt;in this
document&lt;/a&gt;.
-Some of the details outlined there haven&amp;rsquo;t been implemented, yet. E.g. the
+Some of the details outlined there havent been implemented, yet. E.g. the
&lt;code&gt;Build&lt;/code&gt; model does not have the mentioned &lt;code&gt;errored&lt;/code&gt; and &lt;code&gt;cancelled&lt;/code&gt; states, the
-&lt;code&gt;Task::Test&lt;/code&gt; does not have &lt;code&gt;cloned&lt;/code&gt; and &lt;code&gt;installed&lt;/code&gt; states &amp;hellip; simply because the
+&lt;code&gt;Task::Test&lt;/code&gt; does not have &lt;code&gt;cloned&lt;/code&gt; and &lt;code&gt;installed&lt;/code&gt; states simply because the
worker does not support triggering these, yet. These things will probably be
added in a later stage.&lt;/p&gt;
@@ -254,12 +258,12 @@ bunch of columns to migrate from the &lt;code&gt;builds&lt;/code&gt; table to va
(such as &lt;code&gt;commits&lt;/code&gt;, &lt;code&gt;requests&lt;/code&gt;, &lt;code&gt;tasks&lt;/code&gt;) and it seemed easier to come up with a
simple DSL for that than writing all these queries by hand.&lt;/p&gt;
-&lt;p&gt;Also, we&amp;rsquo;re now using &lt;a href="https://github.com/svenfuchs/hashr"&gt;hashr&lt;/a&gt; in the
-application, too (for &lt;code&gt;Travis.config&lt;/code&gt;, specifically). We&amp;rsquo;ve used it in the
+&lt;p&gt;Also, were now using &lt;a href="https://github.com/svenfuchs/hashr"&gt;hashr&lt;/a&gt; in the
+application, too (for &lt;code&gt;Travis.config&lt;/code&gt;, specifically). Weve used it in the
&lt;a href="https://github.com/travis-ci/travis-worker"&gt;worker code&lt;/a&gt; before and it worked
pretty well.&lt;/p&gt;
-&lt;h2 id="in-other-news-"&gt;In other news &amp;hellip;&lt;/h2&gt;
+&lt;h2 id="in-other-news-"&gt;In other news &lt;/h2&gt;
&lt;p&gt;In other news, over the last month we have extract a &lt;a href="https://github.com/michaelklishin/sous-chef"&gt;small project that we use to develop our Chef cookbooks&lt;/a&gt; and
added the following tools to the &lt;a href="https://github.com/travis-ci/travis-cookbooks/tree/master/vagrant_base"&gt;VM infrastructure&lt;/a&gt;:&lt;/p&gt;
@@ -43,12 +43,12 @@ <h1 class="riddle"><a href="/" title="Travis">Travis CI</a></h1>
<h2>A Big Refactoring!</h2>
- <p>We&rsquo;ve just rolled out a big refactoring to the Travis CI <a href="https://github.com/travis-ci/travis-ci">application</a>
-(i.e. the server app which runs on Heroku) that we&rsquo;ve been working on over the
+ <p>Weve just rolled out a big refactoring to the Travis CI <a href="https://github.com/travis-ci/travis-ci">application</a>
+(i.e. the server app which runs on Heroku) that weve been working on over the
last four weeks.</p>
-<p>This refactoring was quite far-reaching and even though we&rsquo;ve tried hard to
-make sure everything works fine there may be glitches and bugs that we&rsquo;ve
+<p>This refactoring was quite far-reaching and even though weve tried hard to
+make sure everything works fine there may be glitches and bugs that weve
overlooked.</p>
<h2 id="why">Why?</h2>
@@ -81,9 +81,9 @@ <h2 id="why">Why?</h2>
<p>You can find more information about the new domain model design <a href="https://github.com/travis-ci/travis-ci/blob/statemachine_merge/docs/notes/build_tasks.md">in this
document</a>.
-Some of the details outlined there haven&rsquo;t been implemented, yet. E.g. the
+Some of the details outlined there havent been implemented, yet. E.g. the
<code>Build</code> model does not have the mentioned <code>errored</code> and <code>cancelled</code> states, the
-<code>Task::Test</code> does not have <code>cloned</code> and <code>installed</code> states &hellip; simply because the
+<code>Task::Test</code> does not have <code>cloned</code> and <code>installed</code> states simply because the
worker does not support triggering these, yet. These things will probably be
added in a later stage.</p>
@@ -99,12 +99,12 @@ <h2 id="why">Why?</h2>
(such as <code>commits</code>, <code>requests</code>, <code>tasks</code>) and it seemed easier to come up with a
simple DSL for that than writing all these queries by hand.</p>
-<p>Also, we&rsquo;re now using <a href="https://github.com/svenfuchs/hashr">hashr</a> in the
-application, too (for <code>Travis.config</code>, specifically). We&rsquo;ve used it in the
+<p>Also, were now using <a href="https://github.com/svenfuchs/hashr">hashr</a> in the
+application, too (for <code>Travis.config</code>, specifically). Weve used it in the
<a href="https://github.com/travis-ci/travis-worker">worker code</a> before and it worked
pretty well.</p>
-<h2 id="in-other-news-">In other news &hellip;</h2>
+<h2 id="in-other-news-">In other news </h2>
<p>In other news, over the last month we have extract a <a href="https://github.com/michaelklishin/sous-chef">small project that we use to develop our Chef cookbooks</a> and
added the following tools to the <a href="https://github.com/travis-ci/travis-cookbooks/tree/master/vagrant_base">VM infrastructure</a>:</p>
Oops, something went wrong.

0 comments on commit 0735f8b

Please sign in to comment.