October 28, 2014
by Jonathan Thorpe, Technical Marketing Manager at Perforce
DevOps Webinar with Gene Kim
If you have ever been tasked with figuring out how to deal with large sets of files or large binaries in a version control system, you’ve probably had problems with performance, reliability and scalability. While there are workarounds that can address some of these issues, the workarounds introduce their own complexity that can be difficult to implement and support.Posted In:
October 24, 2014by Liz Lam, QA Lead Engineer (@p4liz)
I love stories. Each one of us has one to tell. This is the start of a blog series designed to explore the stories of our own Women in Tech at Perforce. It's been fun and inspiring talking to each one of these women. As they share where they've been and how they came to where they are now, it is my hope that others will be encouraged and inspired too.Posted In:
October 23, 2014by Murtaza Amiji, Director of Product Management at Perforce SoftwarePosted In:
October 22, 2014by Julia Angell, Director of Corporate Marketing at Perforce Software
MERGE 2014 is over but all the sessions and awesome content are now available for you to view on-demand. If you attended MERGE you can gain new insights the 2nd time around, see the concurrent sessions from the adjacent rooms, and share these videos with your colleagues. If you didn't make it to MERGE 2014, now’s your chance to see what you missed!
October 21, 2014by Allan Yu, User Experience Designer
We’re excited to announce that we’ve refreshed the UI of our flagship visual client, P4V. Not only did we update more than 200 icons, we also stripped the UI of gradients, shadows and color (where it isn’t meaningful) to make P4V look and feel lighter and cleaner. The user experience is also improved with significantly faster rendering. Don’t worry, though, we preserved P4V’s functionality so these improvements to the UI come at no cost to your productivity. Perforce developers and beta customers alike told us they were able to upgrade without any disruption to their workflow.
October 17, 2014by Sven Erik Knop, Technical Marketing Engineer
Image: PhylB via Flickr
Build engineers need a pristine state of their source material. This particularly means not having any artifacts such as object files or class files leftover from a previous build in the build workspace.
There are several ways to achieve this in Perforce:
- Create a new workspace for each build
- Reuse the workspace by removing all files and forcing a sync, optionally skipping the have-list update for more speed (using the