Category: Tips & Tricks

  • October 10, 2013

    In the days before streams, it was commonly accepted that if files had different names in different branches, you would need to set up a branch spec that mapped one set of file names to the other if you wanted to integrate changes between those branches. When we began developing streams functionality, we knew we would need to provide another way to handle refactoring within streams, since the branch view used to merge changes between a stream and its parent is dynamically generated and is supposed to be a relatively simple function of the paths specified for each stream – hence we came up with a system for matching different filename variants within a source and target to each other and setting up resolves between them.

  • October 08, 2013

    Image: Sewing Daisies w/Flickr

    Posted In:
  • September 30, 2013

    We just threw our first public hackathon, and as you can imagine, we learned a lot in the process. I'd like to share a few of things we learned, so that you can hopefully use some of our experiences in planning your own event.

    1) Have A Hook

  • September 18, 2013

    Image: thatkaringirl w/Flickr

    Over the past few years you might have noticed that we here at Perforce have been building more and more applications on top of the Perforce server; first Chronicle, then Commons, and now Swarm. However our customers have been doing this for over a decade; it turns out that a fast versioning engine that can handle millions of gianormous files is pretty handy to have at the heart of a development pipeline. Heck, some users have embedded Perforce straight into their game engine!

    Posted In:
  • August 28, 2013

    continuous delivery

    It’s becoming increasingly difficult for software developers to keep pace with today’s faster release cycles. What used to be released every 12 or 24 months may now be delivered on the hour. You’ve likely heard about how Continuous Delivery can reduce the distance between a developer making a change and that change benefiting a customer. However, it’s important to remember that one does not simply implement Continuous Delivery—it’s much more of a journey than that.

    To help you on your path, we offer these five tips for Continuous Delivery. Please consider these guidelines for automating and improving development processes across the phases of your delivery pipeline.

  • August 26, 2013

    Sharp-eyed users may have noticed the addition of a new undoc option to the command line client in 2013.2: