Category: Tips & Tricks
July 17, 2013by Bryan Pendleton, Software Engineer
From time to time, people ask me how replica servers affect the security of their Perforce installation.
The good news is that, properly deployed and configured, a replica server is just as secure as your main Perforce server.
It's usually the case that your Perforce server is the most important and valuable server in your entire organization: after all, this is where you are storing everything that you have developed, and everything that your team values! So I'm pleased that you are thinking about security and wondering how replica servers fit into your security process.
July 02, 2013by Russ Tremain, Senior Build Software Engineer
I recently attended MERGE 2013, and happened to attend Matt Attaway’s walk-through of Perforce programming interfaces, entitled Perforce the Plentiful Platform. As Matt quickly established, Perforce provides an incredibly rich set of APIs for implementing build, test, or other automation processes on top of your Perforce source management system.
June 24, 2013by Stewart Lord, Software Architect
If you're reading this, there is a good chance we have a few things in common. One, we both use Perforce. Two, we both make software. And three, we care about our tools. If this isn't you, feel free to move along, but if it is, I'd like to have a little chat.
June 13, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
June 06, 2013by Randy DeFauw
Ever had your Perforce repository become unresponsive because someone ran a script that was hammering the repository in a while(1) loop? The Perforce server process (p4d) is normally a very gracious host, accepting any and all requests from users and automated processes. However, there are some cases where you'd like it to be a little more choosy. Otherwise, a poorly constructed script, malicious activity, or just plain old too much traffic can overwhelm p4d for a period of time.
June 03, 2013by Randy DeFauw
The 2013.1 release of Perforce now supports IPv6 addresses. That means that you can run your Perforce services on an IPv6 address, and use IPv6 addresses in the Perforce protections table. Host names that resolve to IPv6 addresses are also supported.