June 18, 2013by Mark Warren, European Marketing Director, @mark_warren
“Living is easy with eyes closed.” – John Lennon
Many Perforce users have homegrown or ad hoc reporting and dashboard tools built around Perforce server logs and tools like P4toDB. But what if you need a quick overview of the state of a project, codeline, or team?
June 17, 2013by Bob Dever, Senior Director of Corporate Marketing
June 13, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
If you haven't seen already on TechCrunch and Develop, yesterday we released our new code collaboration platform Perforce Swarm. After working on Swarm for many months it's exciting to see the press covering it, but it's even more exciting to see you folks getting your hands on it to see what it can do. While our development team pauses to plan its future development work on Swarm and bask in the glow of the media coverage, I'd like to talk about your future development work on Swarm.
June 11, 2013by Furkan Khan, Director of Product Management
Have you heard the buzz? Our elegant new code collaboration tool is now available. Perforce Swarm is a powerful platform where developers can have conversations about code changes, share creative ideas and help each other fix bugs quickly. Have a look at our 2-minute overview of Swarm.
Swarm is the place to connect to your team, your code and your continuous delivery pipeline. It does three BIG things and a bunch of little (but important) things. I’ll start with the big stuff…
June 06, 2013by Randy DeFauw (@rdefauw)
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.
The 2013.1 release has a great new configuration parameter that lets you prevent these situations. Just set the server.maxcommands parameter to the maximum number of requests that p4d should handle concurrently before it starts rejecting new requests:
June 04, 2013by Nellie LeMonier (@p4nellie)
We make software because we hope someone will use it, that they find it useful, and that it fills a need — even if they don't know they have it. While we can make many incredibly sophisticated, beautiful software applications, many of them will die a lonely death if no users find them useful enough to buy or use. Each of us has had a product die in such a way at least once in our careers. So how can we make software better, more useful, more likely to go viral with users and not die before it lives?