{ "componentChunkName": "component---src-templates-blog-post-tsx", "path": "/blog/2011-09-13-ruby-for-jenkins-goes-pre-alpha/", "result": {"data":{"blogPost":{"title":"Ruby for Jenkins Goes Pre-Alpha","slug":"/blog/2011-09-13-ruby-for-jenkins-goes-pre-alpha/","authorNodes":[{"name":"Charles Lowell","slug":"/people/charles-lowell/"}],"markdown":{"html":"

To quote Dave Bowman, \"something wonderful happened\" last week during the weekly Jenkins-Ruby hack session.

\n

We were able to boot a plugin written in pure Ruby into a Jenkins server just by executing a single command from the command line (rake server). Furthermore, this command did not involve a compilation step, and the plugin that it booted did not bare a trace of evidence that it was to be loaded into a server written in Java.

\n

That's right. Using nothing but good 'ol Bundler and Rake, we hoisted a pure Ruby plugin into the Jenkins runtime.\nAnd I can tell you that after hacking on this for almost a year: it felt... so.... good.... man.

\n

It's not time to declare victory yet, but at least the first two of our major goals have been realized, and that is definitely a cause to celebrate.

\n

Practically, this means that rubyists can check out the source and get hacking without needing any knowledge of\nJava or any Java toolchain. That's why I think it's safe to officially declare the project to be in\na pre-alpha state.

\n

It isn't yet for the faint of heart, and you're sure to find many things confusing and\ndifficult. But at least those who know only Ruby can contribute bug reports, identify pain points, and contribute\nto the creative process.

\n

It's 8:20am, but it still feels like Miller time.

","frontmatter":{"date":"September 13, 2011","description":null,"tags":["java","ruby"],"img":null}}}},"pageContext":{"id":"26960e9e-af2a-5815-8fa4-df3b8e08fa4c"}}, "staticQueryHashes": ["1241260443"]}