P4 Blog

  • November 10, 2014

    Perforce IdentifierAs of the 2014.2 release, the ability to limit your view of the depot by changelist number, previously only available to import paths in streams, has been extended to "classic" client specs with user-defined view mappings.

  • November 07, 2014

    This is part of a blog series designed to explore the stories of our 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 as well.

    Ksenia Burlachenko is our first Hackbright Academy hire. She's been with Perforce for a little over a year. Originally from Siberia, Ksenia was an economics major from the University of Southern California before joining Hackbright. Her loves range from tech and data to economics to film, and everything nerdy in between.

    Posted In:
  • November 06, 2014

    before git rebase

    Merging is a common practice for developers using version control systems. Whether branches are created for testing, bug fixes, or other reasons, merging integrates changes to another location, such as the mainline. To be more specific, merging takes the contents of a single source branch and integrates them with a single target branch. In this process, only the target branch is changed while the source branch history is retained unchanged. With Git, however, there is the second option of rebasing, which is another way to integrate changes from one branch to another. Rebase accumulates a series of changes into a single “patch” and then integrates that patch onto the target branch. Unlike merging, however, rebasing flattens history because it transfers the work done from one branch onto another, destroying the source history in the process.

    Posted In:
  • November 05, 2014

    Automated Testing in Continuous Change Management

    Within an Agile and DevOps environment, Continuous Testing (CT) is the proof of successful merges and continuous integration. At MERGE 2014, the Perforce Conference, I presented our experiences and the best practices we've put in place at Spirent Communications for Continuous-Test (CT) systems. From these experiences and best practices, we have defined the eight attributes necessary for Continuous Test Systems:

  • November 05, 2014

    keep calm and version everything


    Another day, another vulnerability! It seems like only yesterday that sysadmins around the globe were stressfully reacting to Heartbleed. It was interesting to witness that while many were quite anxious over this vulnerability, some groups were not. I’d be willing to bet that those who weren’t stressed-out about Heartbleed were similarly nonchalant about the latest bash vulnerability (aka Shellshock).

  • November 04, 2014

    launching mac desktop
    Image: Jason Corneveaux via Flickr

    A few years ago I switched from a laptop running Windows 7 to a MacBook Pro with OS X. One of the few things that bothered me was that my many Perforce Servers (P4D) I have running on my machine (to be able to quickly demonstrate different configurations such as replication) did not start automatically.

    Posted In: