Search

Continuous Integration: More Than Just A Toolset

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Abstract: Does your team spend days integrating code at the end of a project? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier. But Continuous Integration is more than just a tool like Hudson, TeamCity, or CruiseControl.Net; it is a full development process designed to bring you closer to your source control mainline, increase visibility of project status throughout your team, and to streamline deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.

    Speaker Bio : Jay Harris is web developer and independent software consultant in southeast Michiganthat has been coding in ASP.NET since 2003. He has focused his career on end-user experience and providing quality applications, which has manifested as being a strong advocate of practices and processes that improve quality through code, such as automated testing, continuous integration, and performance analysis. Jay is also active in the developer community, serving as president of Ann Arbor .NET Developers, and organizing a local study group to help area developers pursue Microsoft .NET certifications. When not coding, he is usually blogging to http://www.cptloadtest.com or playing games on his Xbox 360.

    1 Favorite

    Continuous Integration: More Than Just A Toolset - Presentation Transcript

    1. Continuous Integration
      It’s more than just a toolset.
    2. Jay Harris
      Who is this guy?
      What does he do?
      Where did he come from?
    3. Integrating Your Mind
      Scheduled integration is hard
      Continuous integration is easy
      But it is a process, not a tool
      And you should use it all the time
    4. Introduction to CI
      Stay current
      Measure status
      Keep it clean
      Maintain visibility
    5. Effective CI
      Stay current with everyone
      Measure status to keep it green
      Keep it clean with the right tools
      Maintain visibility and accessibility
    6. Martin Fowler’s Vision
      Maintain a single source repository
      Automate your build
      Make the build self-testing
      Everyone commits every day
      Every mainline commit builds on an integration machine
      Keep the build fast
      Test in a clone of the production environment
      Make it easy for everyone to get the latest executable
      Everyone can see what is happening
      Automate the deployment
    7. Implementing CC.Net
      Setting up a CI server is easy
      Show me some code
    8. Standalone Process
      Continuous Integration is not about Agile
      Continuous Integration is not about TDD
      Continuous Integration is not about CC.Net
      Continuous Integration is not about Silver Bullets
    9. More Effective CI
      Code Analysis
      Code Coverage
      Scheduled & Triggered Tasks
    10. Anti-Patterns
      Minimal Feedback & Feedback Spam
      Partial Suite Builds & Bloated Builds
      Infrequent Commits & Bottleneck Commits
    11. Pipelined Builds
      Fail fast
      Slice up the build
      Break apart layers
      But be aware of the dangers
    12. Visibility is key
      Project Managers need to know the status
      Quality Analysts need to know the status
      Developers need to know the status
      You need to know the status
    13. Martin Fowler Reprise
      Maintain a single source repository
      Automate your build
      Make the build self-testing
      Everyone commits every day
      Every mainline commit builds on an integration machine
      Keep the build fast
      Test in a clone of the production environment
      Make it easy for everyone to get the latest .exe
      Everyone can see what is happening
      Automate the deployment
    14. Continuous Integration
      Continuous status
      Continuous feedback
      Continuous availability
    15. Questions?
      Jay Harris
      www.captainloadtest.com
      twitter.com/jayharris

    + Jay HarrisJay Harris, 4 months ago

    custom

    317 views, 1 favs, 0 embeds more stats

    Does your team spend days integrating code at the e more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 317
      • 317 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    -->
    Search
    RSS Feed
    What's new?

    © 2009 SlideShare Inc. All Rights Reserved