BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations What’s Next in Continuous Integration?

What’s Next in Continuous Integration?

Bookmarks
45:59

Summary

Kohsuke Kawaguchi discusses the future of Continuous Integration and Jenkins as they will be influenced by virtualization, cloud computing, DVCS and analysis software.

Bio

Kohsuke Kawaguchi worked for Sun Microsystems, Inc. for about 8 years, and then briefly worked for Oracle. He founded InfraDNA which joined forces with CloudBees. He has been involved in many open source projects, the most notable being Jenkins. You can follow Kohsuke on Twitter as @kohsukekawa.

About the conference

The « What's Next » conference will be the biggest Java event ever organized in France as of 2011, gathering the vibrant French community. It will gather all the most important Java experts of the world around various high-level interventions. The goal of this annual conference is to bring the audience the most up-to-date information on the new and emerging technologies around the Java platform.

Recorded at:

Aug 08, 2011

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Jenkins

    by Steven Dick,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Seems Jenkins is moving aware from pure build into the central management role for all of dev/test/qa environments.

    I've always been impressed by Jenkins low barrier to getting started and now my team have started using the master/slave setup for build and test servers, I'm even more impressed.

    I'll get our guys to look at the dist/fork plugin - that looks interesting.

  • Re: Jenkins

    by Steven Dick,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    And I forgot to say that Kohsuke Kawaguchi is a nice guy - helped me when I couldn't figure out how to use SVN in the early days of Jenkins' predecessor.

  • We will still need to run tests locally, just not all of them.

    by Rex Hoffman,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Just a comment, on about minute 38, around not running tests locally....

    Latency could also be reduced by making tests run quickly.... Devs are always going to need to run tests locally for debugging purposes. So I'd like to see something like osgi/akka/scala in eclipse keeping my code built, and the actors/services/whatever always updated and running so that I can run a test at any time and get near immediate feedback.

    Though I wouldn't run them all locally. :)

    Rex

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT