Innovation at Perforce never stops. Since the last MERGE conference, there have been continual updates across the board in response to user requests. In this session, we're going to look at what's new and take a peek at what's in the works so that you can start planning to exploit them when they're available.
3. 3
Great traction on our enterprise-grade Git solution
Large deployments of our native DVCS
Significant performance improvements in our core
10x growth in code review usage
Helix in simplified Chinese, Japanese, Korean
Significant accomplishments over past 18 months
4. 4
Key market trends and insights from you
Unified experience is key
Teams are distributed Cloud usage on the rise Repository sizes on the rise
Developers prefer DVCS
26. 26
New Path types
• Import @ Change
• Writeable Imports
Stream Spec is Transactional
• Can be staged and submitted with code
Streams Features Streams
27. Create an alias for a
single command or a
chain of commands
Introducing Aliases Productivity
29. Complex Commands
Copyup $(b)
Complex Commands
switch dev && merge --from $(b)
&& resolve -as &&
submit -d "Copied up from $(b)"
&& push
Productivity
30. 30
Clone projects to local servers
Work disconnected
Fetch changes from shared server
Independent local branches
Push changes to shared server
Native Workflow DVCS
38. 38
Access Control Delegation Administration
TeamMembers
Super grants admin
access to depot path:
//helix/united/…
For user TeamLead
Super
Team Lead grants write
access to depot path:
//helix/united/…
For group TeamMembers
TeamLead
39. Git is great, but…
Maximum practical repository size
- Leading to Git sprawl (lots of repos)
Too complex for some contributors
Raises security concerns
Weak visibility across the entire pipeline
DevOps challenges for continuous delivery
Destructible history can be a problem
Git
43. Git is great, but better with Helix
Maximum practical repository size
- Leading to Git sprawl (lots of repos)
Too complex for some contributors
Raises security concerns
Weak visibility across the entire pipeline
DevOps challenges for continuous delivery
Destructible history can be a problem
Scalable Back
End for Git
44. Web Services
Helix
Web App
Desktop
Apps
3rd Party
Apps
GitSwarm
Apps
Versioning
Analytics Security
Notification
Git
Web
Services
Platform
Performance
Scalability
Distributed workflows
Federation
Security
Audit logs
Mono repo
On premise/Cloud
Helix Core
45. 45
Web services provide a standard means of
interoperating between software applications
running on a variety of platforms and frameworks.
Web services can be combined in a loosely coupled
way to achieve complex operations.
Web Services Why Web
Services?
46. 46
Helix Web Services provide the building blocks
• Well defined interfaces
• Consistent data representation
• Common Helix commands
Providing more complex capabilities
• Project Administration
• Project Metrics
• Code Review
Web Services Why Web
Services?
55. New Features
Your own review groups
Batched email notifications
Enhanced search capabilities
Improved differences viewing
Download project content as a zip archive
Swarm
72. 72
Distributed development
Native Git experience &
tools
Built from GitLab
Newest Component
Bidirectional Helix mirroring
Single source of truth
All the Helix –ilities
GitSwarm
73. 73
Hybrid Needed
“
“
GitSwarm
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
74. 74
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
GitSwarm
75. Notable Features
Simple project management
Narrow cloning with Git
Merge-request workflow
Flexible security and administration
GitSwarm
Other clients include: Amdocs, Oracle, Saint Jude's, Barclays, Wargaming, FireEye, U-blox
Large deployments include Samsung (10k with maybe 10k more), Salesforce (1.5k with maybe 1.5k more)
Review groups essentially offer the ability to tailor your own custom activity feed
Batched email fulfills a similar role, tailoring to preference
Make mention of how Swarm is an extensible platform, new integrations being developed all the time.
Mention Slack integration available on our workshop.
As important as code review is, Swarm is evolving beyond it
Unified user experience with everything visible in one place
A single point of contact for many stakeholders, one “surface” to interact with
Create projects in a streamlined UI
Create, import your content (if any), and invite your colleagues
Administer projects directly within the one UI
Manage contributors, change their roles
Even delegate administration authority
Better folder/file browsing experience
Drag & drop UI to copy content locally or add to the project
Create folders/files right from the web UI (2017 feature)
Easier on-boarding: copy some information from the project page and clone
Full DVCS workflow support: clone, work, pull, push
Pure native Git with all your favorite tools, extensions, and aliases
All the Helix clients, plugins, and other tools you expect
The DVCS revolution has enhanced the local experience, but not by doing away with the shared experience.
A recent Gartner report, available free of charge from Perforce, identified both the benefits of DVCS for developer desktops and the need for enterprise management usually provided by centralized VCS.
It’s worth noting that Perforce Helix was one of only two commercial products called out as supporting this hybrid model.
In contrast to what’s already been said:
Helix covers all the workflows and needs across an enterprise from developers to DevOps while protecting valuable intellectual property (IP)
Developers get to use tools they like, even Git and its complete ecosystem if they prefer, which keeps them happy
Helix offers clients suitable for non-developers
And because everything can be in a “single source of truth”, even one big monorepo if desired, DevOps is happy
Helix closes the security holes and even detects threats before IP walks out the door
And provides visibility into the whole pipeline
Allude to Charlie’s discussion of narrow cloning with Helix DVCS, frame the discussion as to how we’ve brought that to Git, an industry first and only.
The latest release of GitSwarm, 2016.1 adds a nice web UI for specifying branches and their paths.
Define as many branches as you like from existing depot paths.
Covers 80% - 90% of the more common use cases.
Other clients include: VMWare, Ubisoft, Microsoft Silicon, NetApp, Boeing Mobility, Kabam (which uses Gitlab EE, moving to GS EE), Vocera, Gracenote (Gitlab user moving to GS), Infinity Ward
Oracle and EMC both have 200 users, prospects of hundreds more
Manage all users on the Helix server
Delegate authentication / authorization to AD/LDAP
Synchronize file permissions and such back and forth