The Perforce Support organization is dedicated to quickly solving time-sensitive issues and giving our customers the tools they need to stay productive with our software. With those goals in mind, we’re very pleased to announce the availability of our new Customer Portal.

Our Customer Portal is a self-service resource that makes it easy to...

As a Perforce user, you have a voice that can shape the future of our products. And we are listening closely. Collecting feedback from our customers to understand their wants and needs is always an important step when defining product roadmaps and prioritizing upcoming features.

A couple weeks ago I wrote about the version control history visualizer code_swarm. code_swarm provides an interesting view of how files connect developers to each other, but it doesn't give any insight into the relationship of the files themselves. To get a sense of how the tree structure evolved over time we can use the popular visualizer Gource.

As a person who loves to tinker and build small, useful tools Swarm is a veritable playground for me. In particular I find the Swarm activity stream is a great place to unify events in my development pipeline in a central place. We've seen how to have external systems create events in the Swarm activity feed, but what if you find yourself needing to create events inside of a Swarm module? Today we'll cover that case.

Last week, GitHub announced capabilities for storing and diffing documents, with the intent to offer versioning capabilities to the non-developer audience.

Version everything, has been Perforce's mantra for quite some time. Brand names such as Salesforce.com, Samsung, Pixar and SAP (the list goes on) have been using Perforce to actively manage digital information beyond source code. That’s because version control is something every knowledge worker battles—whether they know it or not. Ask yourself, "Do you have any files with names containing V1, V2?"