Category: Tips & Tricks
August 12, 2013by Sam Stafford, Developer at Perforce Software
Since the 2013.2 release adds a new piece of file metadata that may need to be resolved when merging (charset, associated with the undoc server.filecharset setting), this seems like a good time for a quick review of all of the different things that "p4 resolve" might ask you about.
The function of resolve, at its heart, is to take changes from a depot file and make sure you've accounted for them in your workspace file. Different commands will schedule resolves for different reasons:
August 08, 2013by Perforce
If you're a heavy user of branches to isolate work intended for different product versions or runtime configurations, you've probably run into this situation. You start working on a branch, make a few changes, merge some upstream work, and then find out you need to move your changes to a different branch. What you'd like to do is merge just the files you've actually modified on your branch, and not bother with the changes that originated in the upstream branch. With the 2013.1 release of Perforce, there's a new way to tackle this problem.
August 06, 2013by Sam Stafford, Developer at Perforce Software
If you do a lot of refactoring, and you notice that your life gets a little bit easier after upgrading to 2013.2 but you can't quite put your finger on why, it just might be one of these changes:Posted In:
August 01, 2013by Stephanie Turner (@p4vsteph)
The topic of code line management and policy makes for some lively discussions. If you ask 10 engineers their opinion, you'll get at least 12 answers.
July 30, 2013by Sven Erik Knop @p4sven
Many Perforce power users and administrators know about counters and attributes already. These are two mechanisms for storing extra metadata in Perforce. The 2013.1 release adds some new power for storing extra metadata, so it's worth reviewing why and how you would use these storage mechanisms.
July 24, 2013by Stewart Lord, Software Architect
Image: Official U.S. Navy Imagery W/Flickr
If you're a true believer in Continuous Integration (CI), you’ve probably tried to run pre-flight builds. A pre-flight build lets you run a pending change through the official CI machinery before you even commit a change, giving you better confidence in your work and helping to prevent broken builds.
There are several ways you could attempt a pre-flight build with Perforce. I’ll cover a few of those here, along with an idea for a purely local build in cases where the build takes a very long time.