Introducing GitSwarm: Pure Git with Globally Scalable DevOps
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 Git is a Very Popular 10-Year-Old — 2015 Stack Overflow Developer Survey 69.3% of developers use Git 2005 2015
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 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 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 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 A Single Source of Truth
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 Hybrid Version Management
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 GitSwarm: Integrated Git Management  Self-service repos  Merge requests  Permissions  Issue tracking, etc. Based on GitLab CE
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 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 Narrow Cloning Helix monorepo Git-sized slice
16 Let’s Have a Look HelixGitSwarm
17 Questions? Charlie McLouth Senior Director Solutions Engineering John Williston Developer Evangelist @p4jbw

Introducing GitSwarm: Pure Git with Globally Scalable DevOps

  • 1.
    Introducing GitSwarm: Pure Gitwith Globally Scalable DevOps
  • 2.
    2 What We’ll TalkAbout 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 aVery Popular 10-Year-Old — 2015 Stack Overflow Developer Survey 69.3% of developers use Git 2005 2015
  • 4.
    4 There’s a Lotto 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 PosesChallenges 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… “ “ Dealingwith 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.
  • 9.
    9 More from Gartner… “ “ Enterprise-grademanagement 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.
  • 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 GitManagement  Self-service repos  Merge requests  Permissions  Issue tracking, etc. Based on GitLab CE
  • 13.
    13 Work Locally, ScaleGlobally  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.
  • 16.
    16 Let’s Have aLook HelixGitSwarm
  • 17.
    17 Questions? Charlie McLouth Senior Director SolutionsEngineering John Williston Developer Evangelist @p4jbw

Editor's Notes

  • #2 Hello everyone, and thank you for attending today’s webinar, “Introducing GitSwarm: Pure Git with Globally Scalable DevOps”.
  • #3 My name is Charles McLouth, I’m the Sr. Director of Solutions Engineering here at Perforce.   And I’m John Williston, Developer Evangelist at Perforce.   Before we begin we wanted to cover a few housekeeping items. At the bottom of your audience console are a number of resources you can use. If you have any questions during the webcast, you can click on the “Q&A” widget at the bottom and submit your question. We will try to answer these at the end of the webcast, but if we run out of time we’ll answer your question via email.   A copy of today’s slide deck as well as additional materials are available in the “resource list” at the bottom of your screen, and we’ll also send the slides from today’s webcast out in a follow-up email at the close of the webcast. In our webinar today, we’d like to introduce you to GitSwarm our Integrated Git Management Solution that we announced earlier this year. The entire webinar will be about 30 minutes with room for Questions at the end. We’ll begin with a short presentation followed by a pre-recorded demonstration.
  • #4 John, tell us about users using Git. <john>
  • #5 John
  • #6 However may of the user benefits of git pose big challenges for the enterprise. These challenges range from the proliferation of git repositories, aka Git Sprawl Breaking projects apart for practical size limitations And raises security concerns as to who has access to what. But the biggest challenge is that encourages silos of data.
  • #7 Silos are bad for DevOps, Dev Managers, and Security professionals. Silos require DevOps to stitch together many sources. Dev Managers lose sight of the development pipeline And security professionals pull their hair out because they have no idea who is accessing what.
  • #8 Gartner Agrees with this sentiment. Distributed Version Control for Teams is more complex to manage for the Enterprise. A small reminder that we’ll be sending out a copy of this Garnter Report after the webinar. Or you can download it now from the Content Resources
  • #9 DevOps, Dev Managers and Security Professionals like a “Single Source of Truth.” This facilitates a singular view for the Development or Deliver pipeline; Provides singular views feeding all automation. And Security can be managed and monitored from a single access point.
  • #10 Gartner recognizes that both are required for efficiency and productivity The freedom and flexibility of DVCS And the security, control, scalability, and visibility of a Centralized Version Control System
  • #11 What Gartner is advocating is something we really believe in as well: A hybrid version control model. <John> That’s right John. But with the power of a centralized system to support your DevOps teams and to help your security teams to sleep at night. And understanding this growing market need is what led to us developing our Helix Platform, which we announced earlier this year.
  • #12 Perforce Helix provides hybrid workflows of DVCS and Centralized Version Control <John> But not at the expense of Enterprise productivity.
  • #13 John
  • #14 Our Secret Sauce allows users to work locally but Enterprises to scale Globally with DVCS and CVCS <John> All backed by the reliability, scalability, and security Perforce has long been known for.
  • #15 Our Federated architecture has been a hallmark we’ve been known for. And this capability has been extended to GitSwarm such that many geographically disparate teams can work with local GitSwarm’s all contributing to Helix and it’s single source of truth
  • #16 GitSwarm offers a lot for DevOps and the Enterprise at large. John, what’s in it for users? <john>
  • #17 Our Demonstration today has been pre-recorded. It will start by giving us an overview and tour of GitSwarm. Then we’ll begin our example demonstration of the marriage between DevOps and Development. Where Developers only wish the source they need and DevOps requires access to all source, compiled results, and in our case our production application environment.
  • #18 Our demonstration showed that you can both have the single source of truth that includes very large binary assets, singular views for automation and continuous delivery pipleline. <John> and as a developer I get a narrow clone of just the source that I need to be productive. <charlie> At this point, we have time to take questions from the audience. I’ll remind you that you can submit your questions using the Q and A panel and we’ll address them. If we don’t get a chance to answer your question we’ll follow up in email. <Q&A> This concludes our webinar today “Introducing GitSwarm: Pure Git with Globally Scalable DevOps”. We thank you for your attendance and wish you a good day.