Developers want the productivity of distributed version control like Git. DevOps benefit from a scalable mainline repository. With our new Helix GitSwarm you no longer need to choose between the two. In this presentation, you will see: - The challenges of using Git at enterprise scale - The conflicting requirements of developers and DevOps - A demonstration of Helix GitSwarm in action

1. Introducing GitSwarm:
Pure Git with Globally
Scalable DevOps

2. 2
What We’ll Talk About Today
 What’s great about Git
 Enterprise challenges
 What works for DevOps
 Helix GitSwarm
 Demo of GitSwarm
 Q&A
2
Charlie McLouth
Senior Director
Solutions Engineering
John Williston
Developer Evangelist

3. 3
Git is a Very Popular 10-Year-Old
— 2015 Stack Overflow
Developer Survey
69.3%
of developers use Git
2005 2015

4. 4
There’s a Lot to Like about Git!
 Enjoy a distributed workflow
 Fast & productive
 Lightweight, local branching
 A great tool for open source code
development and smaller teams

5. 5
But It Poses Challenges to the Enterprise
 Maximum practical repository size
 Git sprawl
 Too complex a tool for non-technical
contributors
 Raises security concerns
 Little visibility across the product
development pipeline
 Creates challenges for DevOps team
practicing continuous delivery

6. 6
Inefficient Product Delivery
 Poor visibility between
teams introduce friction
and design errors
 Poor component reuse
results in higher
production cost
 More delays, less efficient
product delivery
 Increased risk of
quality issues
DevOps

7. 7
According to Gartner…
“
“
Dealing with DVCS from a team
perspective is more complex than
dealing with a central system, and
this complexity is at the root of most
current barriers to broader use.
— Gartner, Inc. Market Guide for Software
Change and Configuration Management

8. 8
A Single Source of Truth

9. 9
More from Gartner…
“
“
Enterprise-grade management of Git
that offers important aspects of a DVCS —
good merging, the ability to work offline
and good collaboration — along with the
security and central repository of a CVCS,
will resolve most remaining concerns
about the use of the DVCS model.
— Gartner, Inc. Market Guide for Software
Change and Configuration Management

10. 10
Hybrid Version Management

11. 11
 Hybrid Workflows
• Distributed & Centralized Version control,
code reviews, simple file sharing
• Happy developers & contributors
 Every File
• Efficiently handles large, often binary, data
 DevOps Stay Happy & Productive
• A mainline source for all builds even with
distributed development
 All IP Safe & Secure
• Granular permissions, theft risk monitoring
Perforce Helix
CONTRIBUTORS
CONSUMERS

12. 12
GitSwarm: Integrated Git Management
 Self-service repos
 Merge requests
 Permissions
 Issue tracking, etc.
Based on GitLab CE

13. 13
Work Locally, Scale Globally
 Distributed environment
for developers
 Git experience and workflow
equivalent to well known tools
 Single source of truth
 Perforce reliability and stability
protecting your assets
HelixGitSwarm

14. 14
Distributed Team Support
 Each developer team
working within its own
GitSwarm ecosystem
 Each team has controlled
access to IP managed
within Helix core
 Team can access only what
they need to do their job

15. 15
Narrow Cloning
Helix monorepo Git-sized slice

16. 16
Let’s Have a Look
HelixGitSwarm

17. 17
Questions?
Charlie McLouth
Senior Director
Solutions Engineering
John Williston
Developer Evangelist
@p4jbw