1 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
CollabNet Enterprise Git Secure, Scalable, Standards-Compliant for the Enterprise
2 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
•Overview of Git
•Enterprise Concerns
•About CollabNet
•TeamForge for Enterprise Git
•Questions
Agenda
3 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
• Open source distributed SCM, used notably by:
– Linux (it was originally developed for that very purpose)
– Eclipse foundation
– Android (based on Gerrit Code Review)
• Why Git?
– All operations are local
• Search, log, history, branching and merging
• Offline development is possible
– Powerful merging strategies (merge, rebase, cherry-pick)
– Ability to develop and deliver differently
Git = Leading DVCS (Distributed Version Control System)
4 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Distributed version control
● Each user has at least one copy (clone) of the repository
● Each 'user' repository holds the full history
● There is a 'Central' repository only by convention
5 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Git Usage Model
add
commit
push
origin
/stable
-1.0
origin
/maste
r
maste
r
add
fetch
clone
Git
origin
master stable-1.0 index working tree
save
save
Local
.git
8 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Git Popularity Continues to Grow, But….
“ The adoption of DVCS has accelerated in small teams, but is moving more slowly in enterprise settings.
Source: Gartner, 27 July 2011 ID Number: G00214153; Hype Cycle for Application Development, 2011; Ian Finley, Mike Blechar
9 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Enterprise Concerns
Anybody (Git using orgs):
• 37% Tool integration (trackers, CI/CD, …)
• 36% Co-existence with other SCM tools
• 33% Security, traceability, process governance
• 16% 24/7 Support and SLA’s
Managers and Above (Git using orgs):
• 51% Security, traceability, process governance
• 49% Tool integration
• 37% Co-existence with other SCM tools
• 22% 24/7 Support and SLA’s
Source: InformationWeek, 2013, http://visit.collab.net/git-survey.html
governance
10 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
• DVCS was created to address a very specific need
• Git has many forks and many usage models
• Can lead to un-connected teams, processes and practices:
– Limiting agility & scale
– Blocking visibility & governance
– Tying up resources better spent on delivering value & innovation
The Issue
11 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Who is CollabNet?
1st Cloud-Based ALM Agile Transformations
Open Agile ALM
1999 2005 2014
Apache / Subversion
2010
Leader • ALM, SCM, cloud, agile
• Transformed 100s of largest, most respected IT orgs
• Enterprise agile experts
– 17,000+ ScrumMasters trained
Pioneer • Creator of Subversion (SVN)
• 1st cloud-based ALM solution
Proven Scale • 10,000+ customers
• 6M+ users
• 280 employees
12 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Industry Leadership
Gartner MQ, ALM
InfoTech Agile ALM Vendor Landscape
“It has the best usage of open source among the vendors
included in the Magic Quadrant, including its Subversion (SVN),
Git, Gerrit and Jenkins, and integration to Black Duck
Software…”
Source: Gartner, Magic Quadrant for ADLM 2013
13 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
24/7 Support Git/Gerrit Training Standards-Compliance Scalability ALM Integration History Protection Code Quality
Advanced Git security Git Projects organization Code-review Replication
TeamForge = Enterprise Git Mgmt. + ALM
Basic SCM features jGit engine Native engine GitWeb
Gerrit
With TeamForge and Gerrit, Git is now ready for the enterprise. Realize all the benefits of Git, without compromising governance, security and compliance.
18 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Git History Rewrite – Functionality in Detail
Commit #1 Initially files added File A added
Commit #2 More files added File B Added
Commit #3 Files modified File A modified
Commit #4 Files Deleted
File A Delete
Change log Change log after History Re-Write
Commit #1 Initially files added File A added
Commit #5 More files added File X added
Commit #1 Initially files added File A added
Commit #2 More files added File B Added
Commit #3 Files modified File A modified
Commit #4 Files Deleted File A Delete
Local git commit(s)
• No traces about deleted changes (commits & metadata associated, files, directories)
• Periodic garbage collection will remove unreferenced commits soon and afterwards they can no longer be recovered
Local Git Repo
git clone
Developer
Commit #1 Initially files added File A added
Commit #2 More files added
Commit #3 Files modified
Commit #4 Files Deleted
Developer Removes some files either by purpose or accidentally
Blessed Git Repo
git push –f origin master
Commit #1 Initially files added
File A added
Commit #5 More files added
File X added
19 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
TeamForge Git History Protection
Commit #1 Initially files added File A added
Commit #2 More files added File B Added
Commit #3 Files modified File A modified
Commit #4 Files Deleted
File A Delete
Change log Change log after History Re-Write
Commit #1 Initially files added File A added
Commit #5 More files added File X added
Commit #1 Initially files added File A added
Commit #2 More files added File B Added
Commit #3 Files modified File A modified
Commit #4 Files Deleted File A Delete
Local git commit(s)
Local Git Repo
git clone
Developer
Commit #1 Initially files added File A added
Commit #2 More files added
Commit #3 Files modified
Commit #4 Files Deleted
Developer Removes some files either by purpose or accidentally
Blessed Git Repo
git push –f origin master
Commit #1 Initially files added
File A added
Commit #5 More files added
File X added
TeamForge History Protect
Detects Rewrite Event
git push –f origin master
1. Notification: Automatic e-mail to administrators
2. Reporting: Temper-proof audit-trail (who, what, when)
3. Recovery: Self-service resurrection of history rewrite
TeamForge automatically secures history snapshots on ‘blessed’ master repository (under “refs/rewrite” or “refs/deleted”), for auditing & recovery.
20 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
• What process will best meet your requirements using Git best practices
• What are your security and governance needs
• What is/needs to be integrated with version control
• What data do you need to migrate
• How do you train your users on Git and process
What to Consider in Moving to Git
21 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
TeamForge ALM Capabilities
Reporting & Governance search
traceability documents
wikis
discussions
Release
Test
Build
Track
Code
Plan
My page
Reports
Projects
Monitoring
My settings
Open ALM
Collaboration Architecture
Communities
My workspace
Deploy
GitEye
Orchestrate
Process Templates
Dashboards & Report Catalog
Desktops
• Integrated ALM development and collaboration tools
• Flexible and repeatable process templates
• Cross-project collaboration architecture
• Reporting & Governance
22 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Associate Git Pushes to Work Items, Jenkins Jobs
23 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
› Git and SVN servers from a single, scalable system
› Centralized access and control of globally distributed Git and SVN repositories
› Enterprise-grade security with RBAC, permissions management, authentication, encryption, auditing
› Enforce code reviews and check-in processes for Git
› Who did what, and what was it related to
With TeamForge, You Gain
› Organization-wide IP discovery, re-use, and reporting
24 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
3-Minute Video on History Protection http://www.collab.net/products/teamforge/git-for-the-enterprise
Software Downloads (TeamForge, Git + clients) http://www.collab.net/git
Git Blogs http://blogs.collab.net/git
Learn More
25 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved. 25 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Questions?
26 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved. 26 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
Thank You
27 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved. 27 Copyright ©2015 Col labNet, Inc. Al l Rights Reserved.
© 2015 CollabNet, Inc., All rights reserved. CollabNet is a trademark or registered trademark of CollabNet Inc., in the US and other countries. All other trademarks, brand names, or product names belong to their respective holders.
CollabNet, Inc. 4000 Shoreline Court, Suite 300 South San Francisco, CA 94080 www.collab.net +1-650-228-2500 +1-888-778-9793 blogs.collab.net twitter.com/collabnet www.facebook.com/collabnet www.linkedin.com/company/collabnet-inc
Top Related