Your SlideShare is downloading. ×
FISL 2010: CruiseControl: the open source that changed the way we develop software
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

FISL 2010: CruiseControl: the open source that changed the way we develop software

1,472

Published on

the practice and the history of Continuous Integration and CruiseControl

the practice and the history of Continuous Integration and CruiseControl

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,472
On Slideshare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CruiseControl: the open source
    that changed the way we
    develop software
    Paulo CaroliAgile Coach
    LuizaPagliariDeveloper
    pcaroli@thoughtworks.com
    Twitter: @paulocaroli
    lpagliar@thoughtworks.com
    Twitter: @lpagliari
  • 2. Agenda
  • 3.
  • 4.
  • 5. Motivation
  • 6. Traditionally, different modules are developed by different teams/developers
  • 7. In XP, any programmer can change any part of the code
  • 8. Definition
  • 9. Continuous Integration is a software development practice where members of a team integrate their work frequently…
  • 10. … each integration is verified by an automated build …
  • 11. … detect integration errors as quickly as possible…
  • 12. … assumes a high degree of tests.
  • 13. Demonstration
  • 14. Solution: continually integrate and
    test throughout the project
    Developers
    Continuous Integration Server
    Source Repository
  • 15. Developers check out code into their private workspaces
  • 16. Developers work on functionality and validate it by running unit tests and local build
  • 17. Developer update code to avoid conflicts
  • 18. Developers work on existing conflicts and validate them by running tests and local build
  • 19. When done, they commit changes to the repository
  • 20. The CI server monitors the repository and
    checks out changes when they occur
  • 21. The CI server builds the system and runs automated tests
  • 22. The CI server releases deployable artefacts
  • 23. The CI server assigns a build label to the
    version of the code that it just built
  • 24. The CI server informs the team of the successful build and generates useful metrics
  • 25. If the build or tests fail, the CI server alerts the team
  • 26. The team fix the issue at the earliest opportunity
  • 27. Continually integrate and test throughout the project
  • 28.
  • 29.
  • 30. C3 project
    4 Dev pairs (Kent, Martin, Ward…)
    Smaltalk / Genstone
    Manual Integration
    Integration server
    Developer name on post-it
    Red / Yellow / Green
  • 31. C2 wiki
    XP is being born
  • 32. XP Explained book released
    Project A
    Martin, Ward and TW
    Java
    Integration was a 2 week exercise
  • 33. < Early 2000 >
    Project A goes for XP
    50 developers, many teams
    Java / Star Team / before ant
    While (true) {
    sleep
    upload?
    build
    test
    }
  • 34. < Late 2000 >
    Martin’s CI article
    Project B
    Repeat the CI automated idea
    CruiseControl is born
  • 35. Project C, D … X
    Connectors to many repositories
    Many contributors
  • 36. CI practice really picking up
    TW in a .Net project
    CruiseControl.Net
  • 37. TW in a Ruby project
    CruiseControl.rb
  • 38. This talk about CruiseControl history
    Many good options!
    Next generation of tools
  • 39.
  • 40.
  • 41.
  • 42. Dashboard
  • 43.
  • 44.
  • 45.
  • 46. Build Indicators
  • 47. Directly on computer...
  • 48.
  • 49.
  • 50. ... Or outside it
  • 51. ... Or outside it
  • 52.
  • 53.
  • 54. CruiseControl
    Cool stats
  • 55. The oldest running CI build
    (August 2000)
  • 56.
    • From 2006 to2010
    • 57. 74% green builds
  • Last 5 months: 41,000+ downloads
    Countries
    O.S.
    1. US 10,526
    2. China 7,637
    3. India 3,154

    10.Brazil 678
  • 58. 600,000+ downloads(21.5 TB) since 2001
  • 59. CruiseControl: the open source
    that changed the way we
    develop software
    Questions?
    Thank you!
    Paulo CaroliAgile Coach
    LuizaPagliariDeveloper
    pcaroli@thoughtworks.com
    Twitter: @paulocaroli
    lpagliar@thoughtworks.com
    Twitter: @lpagliari
  • 60. References (Google it!)
    XP Explained by Kent Beck
    Continuous Integration by Martin Fowler
    Continuous Delivery by Jez Humble and David Farley
    CruiseControl by the community
    Bubble, Bubble, Build's In Trouble (lava lamp)

×