Make Subversion Agile

Make Subversion Agile in aDistributed Development

Environment

Steve BerczukAgile Expert and Author

Jim CampigliVP Product Marketing

QUICKPOLL

What agile methodology are you using now?

○ Scrum

○ XP

○ Other

○ Not using agile

QUICKPOLL - RESULTS

What agile methodology are you using now?

○ Scrum

○ XP

○ Other

○ Not using agile

Environment

Steve BerczukAgile Expert and Author

AGENDA

• Agile Basics

• How SCM Enables Agile Teams

• Distributed Agile Challenges

• Review

Steve Berczuk

• www.berczuk.com/blog

• www.scmpatterns.com

• steve@berczuk.com

Agile and SCM

• Communication

• Collaboration

• Feedback

• Agile and SCM establish a framework to

– Enable focus

– Eliminate distractions

Agile Manifesto

•Individuals and Interactions over Processes and Tools

•Working software over Comprehensive Documentation

•Customer Collaboration over Contract Negotiation

•Responding to Change over Following a Plan

Good SCM is essential for Agile Software Development

What is Agile?

• Incremental and Iterative– Feedback, Adapt

– Focus on delivering value

• Self-Organizing Teams– Commitment

• Communication

• Working Code– Tests

– Integration

– Private Workspaces

Agile is…

• Values:

– Communication

– Feedback

– Working Code

• Tools:

– Continuous Integration

– Version Management

– Automated Testing

Software Configuration Management

• SCM Functions

• SCM & Agile Teams

What is SCM?

• Functions:– Identification

– Control

– Status Accounting

– Audit and Review

• Activities:– Getting Code

– Building

– Branching and Merging

• Communication

• Working Software

Agile Development

Repository

SCM & Agile Teams

• Coordination

– Version Management

– Build Management

– Testing

• Essential Function with Low Overhead

Distributed Teams

• Challenges

– Communication

– Feedback

• Integration

• SCM tools and processes can help

SCM In Context

Distributed Agile Success Factors

• Project Management

– Shorter Sprints

• Engineering Practices

– Integrate Frequently

– Test

• Review and Retrospect

• Tools Help

• Process/Workflow First

• Qualities– Fast

– IDE Integration

– Issue Tracking Integration

– Build Integration

– Automation

• People are Human

Summary

• SCM Tools and Practices Enable Agility

• Distributed Teams -> Communication Challenges

• Version Management & CI are communication

More Info

• Software Configuration Management Patterns: Effective Teamwork, Practical Integration by Steve Berczuk & Brad Appleton

• Continuous Integration: Improving Software Quality and Reducing Risk by Paul Duvall and Andy Glover

• CM Crossroads: www.cmcrossroads.com

Thank you!

For more information:

Steve BerczukEngineer, Humedica

steve@berczuk.comwww.berczuk.com

www.berczuk.com/blogwww.scmpatterns.com

QUICKPOLL

Is your development organization…?

○ Local to one site

○ Regional

○ National

○ International

QUICKPOLL - RESULTS

Is your development organization…?

○ Local to one site

○ Regional

○ National

○ International

Environment

Jim CampigliVP Product Marketing

AGENDA

• Central Server Architecture

• Proxy Server

• Subversion MultiSite

• Subversion Clustering

• Summary

Central Subversion Server

• Central servers can’t support agile in large distributed environments.

– Slow networks cause remote sites to checkout and commit infrequently.

– Continuous build integration becomes impractical

– Single point of failure architecture limits availability.

Proxy Server

• Proxy server solutions have the same network performance issues for commits and other writes.

– Remote sites can’t perform builds locally if write steps are involved.

– Master server is a single point of failure for commits and other writes.

– No guarantees of transactional consistency between master and slave servers.

Subversion Multisite

• Continuous communication.

– Latest changes are available everywhere at LAN-speed.

– Merge conflicts are caught and fixed when they occur.

• Continuous build integration.

– Each site can perform builds and test locally with the latest code.

Subversion MultiSite supports distributed agile by enabling:

Subversion MultiSite

• Peer-to-peer architecture with no single point of failure.

• Subversion repositories connected over aWAN synchronize automatically with eachwrite operation.

• Developers at all locations experience LAN speed performance for both read and write operations.

• Built-in hot backup and automated disaster recovery features make third party solutions completely unnecessary.

• Transparent implementation doesn’t change Subversion’s behavior, so there’s no retraining.

Subversion Clustering

• Allows Subversion servers to bedeployed in an active-active cluster.

• Same replication technology asSubversion MultiSite.

• Offload build process from development servers at large sites.

• Latest changes from development serversare available on build servers.

• Shared nothing clustering

– No sharing of disk, memory or CPU.

• No single point of failure.

– Even load balancers can be made redundant.

• The cluster appears to end users as a single Subversion server.

• Intelligent load balancing for optimal performance.

• Failover is transparent and immediate.

• Can be implemented in combination with Subversion MultiSite.

• Local clusters can be combined into aactive-active WAN cluster.

• Entire solution can be monitoredand administered fromone location.

Customers

Summary• Unique technology allows distributed teams to work as one at LAN-speed over a WAN, not in silos.

• Subversion MultiSite supports distributed agile development by enabling:

– Continuous communication

– Continuous build integration

– High availability with no downtime.

• All servers can be monitored and administered from a single location.

• Subversion Clustering combines intelligent load balancing with WANdisco’s unique technology to remove the performance bottleneck of a central server and eliminate downtime at a single location.

• Subversion Clustering can be implemented standalone or in combination with Subversion MultiSite to enable local clusters to be combined into an active-active WAN cluster.

• Both solutions make full 24X7 operation possible.

• Both solutions feature a transparent architecture that eliminates retraining.

Questions and Next Steps

• For more information on Subversion or to request a copy of slides used in today’s presentation, please contact:

– Email: sales@wandisco.com– Web: www.wandisco.com– Phone: 866 846 0404 (U.S.)– Phone: +44 (0)114 3039985 (Europe)

Join the Subversion Community today!http://subversion.wandisco.com/

Learn more about Subversion services and traininghttp://wandisco.com/svn/services

Make Subversion Agile

Technology

Subversion Introduction

Subversion Clase

Subversion - Nikola Brežnjaknikola-breznjak.com/portfolio/Subversion_en.pdf · 4 Where to use Subversion? Problems: • During the development of some program you make a few versions

Subversion (SVN)

Version Control with Subversion - For Subversion 1to publish a full-length Subversion book, the path of least resistance was obvious: just expand the Subversion handbook. The three

subversion spanish

Make IT Simple, Make Business Agile - HTE

Install Subversion

Introduction to Subversion - multithread.orgmultithread.org/files/presentations/subversion/subversion_tutorial.pdf · What is subversion? Subversion is a free/open source version

Make IT Simple, Make Business Agile ——Huawei IT New Products

Make IT Simple, Make Business Agile

Beyond Scrum: Scaling Agile with Continuous Delivery and Subversion

Subversion client

Comparison: Perforce and Subversion Perforce · Comparison: Perforce and Subversion 4 Overview Attribute Subversion Perforce Branching, Merging, and Release Management Subversion

De Subversion

Operation: Make Marketing Agile

Comparison: Perforce and Subversion · Comparison: Perforce and Subversion 4 Overview Attribute Subversion Perforce Branching, Merging, and Release Management Subversion offers branching,

Subversion FAQ

Using subversion

Version Control with Subversion Quick Reference of Subversion