Sasha Labourey on continuous integration environments

Sasha Labourey on continuous integration environments

Sasha Labourey on continuous integration environments

date:Sep 23, 2010

Interview with Sasha Labourey, former JBoss CTO, who just started a new company, CloudBees offering Hudson as a service. Labourey discusses continuous integration environments.


Read the full transcript from this video below:  

Sasha Labourey on continuous integration environments

Sacha Labourey:           Sacha Labourey, CEO and founder, CloudBees.

Interviewer:     Sacha, tell us why continuous integration is such a pain point for developers.

Sacha Labourey:           Developers need continuous integration to do their job, but they do not need the hassle of maintaining a continuous integration environment.

Interviewer:     What kind of problems pop up during continuous integration?

Sacha Labourey:           Typically, when you start using continuous integration, you start with a single machine, but very quickly, you need more machines to handle that load. You get hooked onto continuous integration, and that is where the work starts growing in a non-linear fashion. You need to devote more time to install and maintain those machines, make sure they are all updated at the same level, and that takes you time. Sometimes your job gets stuck, so you need to react to that, and without realizing, you start dedicating quite a bit of time to your continuous integration environment, when actually, you should be focusing your time on development.

Interviewer:     What is CloudBees' approach to solving this?

Sacha Labourey:           At CloudBees, we totally remove those issues from the table. We take Hudson, the preferred de facto Java continuous integration server, and we provide it as a service, so it is what we call Hudson-as-a-service. We maintain Hudson for you. You have your own dedicated instance; you get also your own kit and subversion repositories, maven repositories, and the good thing is that you get as many build agents as you want. Let us say you start ten jobs at the same time. We allocate, in a snap, ten machines to your master. You have those ten jobs running, as soon as they are over. We detach those machines, and you stop paying for them. Essentially, you have nothing to maintain, you get as many machines as you want, and you just pay for what you are using, actually.

Interviewer:     Great, thank you.

Sacha Labourey:           Thank you.

More on Integrated development environments