Category: Tips & Tricks

  • March 27, 2013

    Are you rolling out Git Fusion to a large number of users? If so you will probably find that administering the SSH keys is one of the bigger challenges. In a perfect world users would be able to easily add and delete their public keys themselves, but it takes a bit of work to get them into the server as users need to map a portion of the Git Fusion depot in a client spec and then add the file.

    Posted In:
  • March 05, 2013

    Find yourself juggling a lot of Perforce connections in P4V? It's not uncommon for companies to silo unrelated code in multiple Perforce servers for simplified security and to minimize IP visibility, but this can mean developers who cross the boundaries have to bounce between a number of different Perforce servers to do their job. To make this workflow a bit easier, P4V supports "Favorite Connections" which can have more descriptive names than just a port, user, and client slammed together. Let me show you how to set this up.

    First go to the “Connection” menu and select “Favorite Connections”.

    P4V's favorite connection menu

    Posted In:
  • January 31, 2013

    Everyone has preferences. Whether it's personal or professional, we all have our own ways of doing things. Being a command-line gal myself, I will always prefer using the keyboard over my mouse. There are those who like to drag-and-drop and those who like to right-click. For our Visual Studio plug-in users, we also have a toolbar option.

    Posted In:
  • January 10, 2013

    One of the hidden gems in P4VS, the Perforce Visual Studio plug-in, is using shelves for a simple code review system. It's easy, you don't need any extra tools, and there's a little enhancement coming in the next P4VS version in the next few weeks.

    Let's say I've got a few files checked out in P4VS:

    code review perforce visual studio

  • December 13, 2012

    git fusion logoI've been using Git Fusion for real work for a few weeks now. Using Git (and P4Sandbox) is great for me, since I'm a remote worker who travels a lot.

    Posted In:
  • December 11, 2012

    Are you using a task branching workflow? If so, merging is a routine part of your development workflow. Hopefully, those merges are fast and automated. The more often you merge, the smaller the merge is and the less chance you have a painful conflict to deal with.

    If you're a release manager or branch guru, that's part of your consideration as you think about your branching model: how efficiently and easily are the changes flowing between branches?

Pages