Following on from the new company strategy, we will take a look into the priorities for the Perforce development team. Sharing the product roadmap for the next 12 months and recent updates made to make Helix continue to meet the demands of all our global customers.

2. Embracing Git and
Distributed Teams
Ralf Gronkowski
Technical Sales Manager

3. Git Adoption
— 2015 Stack Overflow
Developer Survey
69.3%
of developers use Git
2005 2015

4. Developers love Git
•Enables fast local branching
•Offline capabilities
•Support for Git Everywhere
•The Git Generation!

5. 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

6. 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
 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

7. 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

8. 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>]

9. git p4 demo

10. 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

11. 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

12. Git Fusion demo

13. GitSwarm: Integrated Git Management
•Self-service repos
•Merge requests
•Permissions
•Issue tracking, etc.
Based on GitLab CE & EE

14. Mirrored to the Helix Versioning Engine

15. 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

16. GitSwarm demo

17. 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

18. Ralf Gronkowski
rgronkowski@perforce.com
Q&A