embracing git and distributed teams

Embracing Git and Distributed Teams

Ralf Gronkowski Technical Sales Manager

Git Adoption

— 2015 Stack Overflow Developer Survey

69.3%

of developers use Git

2005 2015

Developers love Git

•Enables fast local branching

•Offline capabilities

•Support for Git Everywhere

•The Git Generation!

What companies tell us…

•There can be challenges with repository size

•High volume of Git repos

•Non code contributors may struggle with CL

•Security is becoming an increasing priority

•Enhanced visibility is needed across the entire development pipeline

•Immutable History is needed

Perforce Helix embraces Git

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

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

• Auditing

The Perforce Git journey so far

git p4 (2007)

Git Fusion (2012)

GitSwarm (2015)

Future (2017 and beyond)

•unification

•performance and scalability

•interoperability with git ecosystem

git p4

•Available for a long time

•Build by the git community and actively maintained

•Requires a p4 client on the desktop

git p4 clone [<sync options>] [<clone options>] <p4 depot path>… git p4 sync [<sync options>] [<p4 depot path>…] git p4 rebase git p4 submit [<submit options>] [<master branch name>]

git p4 demo

Git Fusion

•Translates git commits to p4 changelists

•Translates p4 changelists to git commits

•Introduced slice and dice of repos, aka narrow cloning

Git Fusion

Git Fusion improvements (10 releases)

•Performance

•Support for non-linear history

•Support for Submodules from Stream imports

•Support for Git LFS

•Support for post- and pre-commit reviews with Helix Swarm

Git Fusion demo

GitSwarm: Integrated Git Management

•Self-service repos

•Merge requests

•Permissions

•Issue tracking, etc.

Based on GitLab CE & EE

Mirrored to the Helix Versioning Engine

GitSwarm improvements (6 releases)

•“Embedding” a Helix versioning engine

•Mirroring of Git repos with Helix

•Import existing repos from Helix

•UI to browse Perforce Helix and create Git Fusion repo configurations

•Enabling and disabling mirroring

GitSwarm demo

Directions for the future

•Unification - pulling our Git experience and tools into a single UI

•Performance and scalability – further optimizing the user experience and scaling with enterprise needs

•Interoperability with the wider Git ecosystem - helping you collaborate with other development teams / companies …whilst maintaining a Secure Single Source of Truth

Ralf Gronkowski

rgronkowski@perforce.com

Q&A