February 10, 2012
by Randy DeFauw @rdefauw
Over the last several years, Perforce has steadily improved its data replication technology. That’s good news if you have teams working in different parts of the world, or want to take advantage of development tools that put a lot of load on version control, like build automation. In other words, if you’re anywhere near modern software development, Perforce replication is good stuff.
January 13, 2012
by James Creasy
"Use the right tool for the job." my father would say, as he hammered a screwdriver into a rusted set of brake drums.
Of course, if you don't have a chisel, you make do with what you have at hand. But when a tool better suited for the task at hand comes along, you are smart to start using it.
October 12, 2011
by Randy DeFauw
Distributed development can mean a lot of things depending on the context. I think of it as two related but distinct areas. I'd like to dive into those areas and talk a bit about how P4Sandbox will help both cases.
June 06, 2011
by Alexandra Weber Morales
Nothing cements customer loyalty like coming through for them in a pinch. That’s what happened when Perforce support and development was able to implement a reference solution for Research in Motion (RIM) in just two weeks.
February 08, 2011
by Rusty Jackson
Would you like a faster way to promote your code than p4 integrate and then a p4 resolve -at? If so, then check out the new "p4 copy" command in 2010.2! It does the whole process without looking at integration history.
As a nice side benefit, it will make sure you are getting a correct promotion without having to do extra diff steps after the integrate to look for ignores in the integration history because it is doing the integrate based on diffs between the two branches. A great new 2 for 1 command. Performance and less work to do a "copy up" integrate.
February 02, 2011
by Rusty Jackson
With 2010.2, you now have an easy way to maintain a DR server for your main Perforce server. Here is a quick overview on how to set one up:
Configure a second server exactly the same as your primary server. Same volumes, Perforce settings, everything. This is essential for making sure that all your triggers, depot mappings and everything work on the DR server.
Now you are going to create all the required entries in the configuration table on the master server as follows: