scaling git for the enterprise

AW2 Agile Development Concurrent Session 11/12/2014 11:30 AM

"Scaling Git for the Enterprise"

Presented by:

Bob Aiello CM Best Practices Consulting

Brought to you by:

340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com

Editor-in-chief of CM Crossroads and author of Configuration Management Best Practices: Practical Methods that Work in the Real World, Bob Aiello is a consultant and software engineer specializing in software process improvement, including software configuration and release management. He has more than twenty-five years of experience as a technical manager at top New York City financial services firms, where he held company-wide responsibility for configuration management. Bob served as vice chair of the IEEE 828 Standards Working Group on CM Planning and a member of the IEEE Software and Systems Engineering Standards Committee Management Board. Contact Bob at bob.aiello@ieee.org, via LinkedIn, or visit cmbestpractices.com.

Scaling Git for the Enterprise

Bob Aiello, Principal Consultant and Author of Configuration Management Best Practices : Practical Methods that Work in the Real World

http://www.linkedin.com/in/BobAiello http://cmbestpractices.com

Who am I? • CM Lead & Consultant for over 25 years • Technical Editor CM Crossroads 15 years • Aapril uthor of CM Best Practices • IEEE Standards Management Board • Tools and process agnostic • The guy who supports large scale version control systems! 2 Nov 12, 2014 http://cmbestpractices.com © 2014

Goals of this Presentation • Develop secure and reliable VCS • Create scalable strategy for support • Plan for costs and resource requirements • Understand the VCS ecosystem • Support advanced functionality • Establish SCM processes • Support the ALM! 3 Nov 12, 2014 http://cmbestpractices.com © 2014

Goals of Code Management

• Never lose code • Know exactly what is running in Prod • Make a two line fix without any chance of the code regressing (due to the wrong version) About SCM…

Source Code Management

• Control of every configuration item (e.g. source code, config, binaries, compile and runtime dependencies). • Much more than just checkin and checkout (version control) • Provides sanity to the development process (reduces cognitive complexity)

Why Git?

• Simple & Reliable • Distributed (actually decentralized) • Cloning vs checkout • Branching and merging • Storage is very efficient • Deployment What about the dark side? http://cmbestpractices.com © 2014 Nov 12, 2014

Dysfunctional Git

• Often setup on R&D servers • No built in support for LDAP • Rewrite history • Editing logs creates audit issues • Cottage industry to address Git shortcomings

Git in the Cloud

• Scalable infrastructure • Experienced administration • Focus on your real job • Advertising your project • Distributing and deployment

Cloud Based Providers

• Github – millions of users • Bitbucket – over a million users • Enterprise Git • Many other cloud based providers • Changing landscape

Infrastructure

• Familiar servers • Scalable (plan for growth) • Installation procedures • Using Puppet to install Stash • Manage licenses • Entitlements Hybrid approach…

Hybrid Cloud

• Start with Cloud based providers • Setup your own infrastructure • From QA onwards

Git Stash is a popular choice…

Git Stash

• Host on your servers • Your favorite cloud • Supports LDAP • Backend in database • Scalable infrastructure • Establish IT controls

When Dev sets up Stash

• Lack of controls • When I asked for a checklist… • Milestone releases go to secure repo • Establish the definitive media library

Planning

• Resource estimates • Charge back for projects • Licenses • Disk, servers, OS • Chargeback for server administration

Establish the Use Case

• Clear and consistent way to use Git • Developers tend to do whatever worked well on the last project • Result is that everyone is doing something different

Defining the Usage Model

• You need to create a clear and compelling usage model • Otherwise everyone will do whatever worked well on the last project • Helps even when you have to live with an inferior tool

Variant Management

Variants in the code

• Supporting multiple operating systems

Training

• Training establishes consistent practices • Essential for variant management • Key for release and deployment

Training

• Training is the “hill to die on” • Best when given by your CM support team • Includes the process you want them to use • Much more than just vendor training • Test first and then teach

Defect & Task Tracking

• Track changesets to workitem • Traceability to who made the change • Makes release notes a breeze to create • Ties back to requirements and test cases • Allows for ALM and workflow automation http://cmbestpractices.com © 2014 Nov 12, 2014

Task Based Development

• Integration with task and defect tracking • Planning should be upfront • Traceability and support for the ALM

Ensuring the Trusted Base

• Know what you built • Deploy the right code • Verify that it got there • Detect any unauthorized changes CM is a full lifecycle endeavor

Getting Started

• Always best when to start small • Remember agile and lean principles • Iterative approach to establish process • Make decisions at last responsible moment http://cmbestpractices.com © 2014 Nov 12, 2014

Feedback loops

• What is working and what needs to be improved • Assess your team’s practices • Plan for change

Commercial Tools

• Vendors have learned to coexist with open source • Commercial tools often have more features • Driven by customer feedback

Continuous Integration

• Drive your CI builds from Git/Stash • Use Git to provision and configure your servers • Git integrates with most CI servers

Continous Delivery

• Automate your application build • Package automation • Deployment automation • Delivery versus deployment

Process Improvemet

• Survey your customers • Take input and plan for improvement • Remember to be have a promotion system for your VCS

Assessment

• Ask what works well • Assess existing best practices • Create roadmap and plan for improvement

Goals of this Presentation • Develop secure and reliable VCS • Create scalable strategy for support • Plan for costs and resource requirements • Understand the VCS ecosystem • Support advanced functionality • Establish SCM processes • Support the ALM! 31 Nov 12, 2014 http://cmbestpractices.com © 2014

Scaling Git for the Enterprise

Bob Aiello, Principal Consultant and Author of Configuration Management Best Practices : Practical Methods that Work in the Real World

http://www.linkedin.com/in/BobAiello http://cmbestpractices.com

scaling git for the enterprise

Software

scaling agility across the enterprise

scaling devops from ground zero to enterprise

scaling the lean startup in the enterprise

scaling devops to the enterprise

enterprise git

enterprise git adoption webinar - chinese

enterprise software - scaling up sales

scaling enterprise wireless lan deployments

scaling agile in the enterprise

scaling agile. agile across the enterprise

git at an enterprise

starting and scaling devops in the enterprise

scaling agile at enterprise chema garcia

endevor-scm-wp101 bridging your enterprise git server with

scaling enterprise sem campaigns - smx muenchen 2016

scaling agile for distributed enterprise organizations

scaling complexity in wordpress enterprise apps

scaling git with bitbucket data center

git adoption in the enterprise - microfocus.com

scaling git - stefan saasen