Excellent news for Github users

CloudBees release BuildHive – Jenkins-based CI build tool for GitHub,

Chris Mayer

Straight out of the Jenkins User Conference, creator Kohsuke Kawaguchi had a big announcement – uniting continuous integration builds with GitHub repositories

Rejoice GitHub users, your prayers have been answered by the
guys behind continuous integration server Jenkins. Yesterday at the
Jenkins User Conference in New York (the second stop on the world
tour), creator Kohsuke Kawaguchi revealed his latest project
a free service that lets you set
Jenkins-based continuous
integration build/test jobs for your GitHub repositories with just
a few mouse clicks.

Initially beginning as a Christmas side project, BuildHive soon
spawned into a much bigger project under CloudBees. Powered by
Jenkins, BuildHive aims to hook up to all that’s good about GitHub
and make it a simple as possible to get CI jobs underway. Although
tailored towards Java projects initially (so Ant, Maven and
Gradle), there’s also the possibility to try BuildHive with some
Ruby projects as well.

It’s a simple 3-step

  1. Click the “login” link on the top right corner to login to
    BuildHive. You’ll be asked to authorize BuildHive to retrieve
    information from your GitHub repositories.
  2. Click the “create project” link from the left and pick
    repositories for which you want to setup CI jobs by pressing the
    “click to enable” button
  3. Push changes to your repository via Git, and watch them

As the diagram above shows, the BuildHive homepage has a sleek
look, with failed and successful builds scrolling across the top,
almost looking like trading cards. They got blue if successful and
red if they’ve failed – easy to grasp. At the time of writing it
was a sea of red, but with time, you’d expect this to filter out as
people get to know BuildHive better. 

In a
, Kawaguchi discusses how BuildHive extends the
capabilities of Jenkins:

Behind the scene, many of the features in BuildHive rely
value-add plugins for Jenkins Enterprise by CloudBees
which are available for customers to use on their own Jenkins
instances. For example, we use the 
 to model various project types and for
auto-sniffing. We use the 
Merge plugin
 to speculatively build pull requests.
So, while it isn’t as easy as it could be, our customers can set up
a similar environment in their own Jenkins instance, or they can
re-use those pieces to create similar but different

There’s only a small amount of activity currently going on, but
it’s only a day on from the announcement – we expect many to use
this intriguing CI shortcut very soon, and that it will continue to
grow with more open source plugins coming into play. For a debut,
it’s a terrific piece of kit, essential for any Jenkins/GitHub

Congratulations Jenkins commmunity for once again thinking
outside the box.

comments powered by Disqus