P4 Blog

  • May 11, 2015

    Our Cygwin license has expired and due to the low demand for Cygwin platform builds we are not renewing it. All Cygwin builds have been pulled from our site in compliance with the license. However if you are a stalwart fan of Perforce and Cygwin all is not lost! Let’s look at your options.

    Using the Windows p4:

    There is a function that many folks in the Perforce community have used for awhile now to avoid installing two p4 executables on their machine. In Cygwin you can add the following function to your .bashrc:

    p4() { PWD=$(cygpath -wa .) "/cygdrive/c/Program Files (x86)/Perforce/p4" "$@"; }

    This will allow you to use the regular Windows build of p4 from inside of Cygwin.

    Posted In:
  • May 07, 2015

    Last year I published a blog article Lightning Fast Syncs where I described how to improve the performance of p4 sync when there was network latency involved. The abbreviated version is that we enabled compression, increased the network buffer sizes, and fetched files in parallel. The tests included a mix of text and binary files totaling 135MB with 140ms latency. I think it served as a very good reason to upgrade.

    Posted In:
  • May 06, 2015
    With all the big changes in the 2015.1 release you might have missed some of the smaller features potentially saving you precious time (and keystrokes). Here are ten of them, fresh from the release notes:
  • May 04, 2015

    Like they say, a chain is only as strong as its weakest link. Your versioning infrastructure is part of your application development lifecycle setup, and you will want to make sure that all security measures are in place to safeguard your precious digital assets from theft.

    Posted In:
  • May 01, 2015

    If you’re reading this, odds are good you’re using Perforce Helix for a reason: to build products that your customers want to use. Here at Perforce, our User Experience (UX) team is constantly engaged in user research to learn more about our existing and potential customers, so we know we're building products that solve real problems.

  • April 29, 2015

    Here at Tula Technology, we develop fuel efficient technologies for gasoline powered automotive engines. We adopted Perforce over two years ago for source control of Dynamic Skip Fire (DSF) technology running on a coprocessor of the Engine Control Unit. During that time, we have used Perforce successfully on multiple automotive projects and it has been the key to our success in a complex development environment.

    Posted In: