Permalink
Browse files

it's "jenkins", not "jankins"

  • Loading branch information...
1 parent 0bc7ee6 commit 92f0dc4e21186a4a2f26959be41137ce5ff342bc Sven Fuchs committed Feb 12, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 2011/2/5/travis-a-distributed-build-server-tool-for-the-ruby-community.html
@@ -31,7 +31,7 @@
</ul>
<p>All of these building blocks might change in the future, but here&#8217;s an <a href="http://github.com/svenfuchs/travis/raw/master/docs/travis.spike-2.png">overview</a> of how they currently work together. And here&#8217;s a short screencast (the UI has changed a bit in the meanwhile but you&#8217;ll get the idea): <a href="http://www.youtube.com/watch?v=mNOwCJhjWAw" title="spike 2">1:20 quick demo screencast</a></p>
<h2>The vision</h2>
-<p>Maybe <a href="https://github.com/jenkinsci/jenkins">Jankins CI</a> (formerly Hudson) is the best open-source build server tool for Ruby projects out there today and everybody seems to be using it. Or maybe that&#8217;s just my impression. In any case my feeling is that it just isn&#8217;t a particularly good fit to the Ruby community for a couple reasons.</p>
+<p>Maybe <a href="https://github.com/jenkinsci/jenkins">Jenkins CI</a> (formerly Hudson) is the best open-source build server tool for Ruby projects out there today and everybody seems to be using it. Or maybe that&#8217;s just my impression. In any case my feeling is that it just isn&#8217;t a particularly good fit to the Ruby community for a couple reasons.</p>
<p>Instead, imagine a simple and slim build server tool that is maintained by the Ruby community itself (just like Gemcutter is, or many other infrastructure/tool-level projects are) in order to support all the open-source Ruby projects/gems we&#8217;re using every day.</p>
<p>Why not have a very slick application that loads off all the heavy work to workers &#8211; and have workers started on boxes contributed by the community itself. A lot of people have underused boxes idling at their offices or somewhere else. Why not make it easy for them to contribute run-time on these boxes for building open-source Ruby projects they use every day. I am sure many people would love this kind of opportunity of giving something back. On top of that one could even post a tiny message alongside with builds that ran on their boxes (a la &#8220;this build was kindly sponsored by [link to their website]&#8221;) to make this even more appealing.</p>
<p>A system that uses a client-side JS frontend, websocket messages and a tiny <span class="caps">JSON</span> <span class="caps">API</span> will make it easy for people to come up with alternate UI implementations. The current implementation of Travis should already allow building a custom dashboard or mobile app pretty easily.</p>

0 comments on commit 92f0dc4

Please sign in to comment.