November 12, 2013by Matt Attaway, Open Source Community Manager (@p4mataway)
I think 'p4 edit' is by far the most cursed Perforce command on Twitter. Folks coming from Subversion and Git are accustomed to an implicit checkout workflow, and being forced to ask the version control system for permission to change something is grating. Conveniently, Perforce supports implicit checkout as well! Let's take a look.
November 07, 2013by Carrie Ewing, VP of Operations
Perforce Software and our employees owe much of their success to the communities in which we live. The Perforce Software Foundation exists to share this success with the charitable organizations that make the communities what they are.Posted In:
November 06, 2013by Nathan Fiedler, Software Engineer
Git Fusion’s goal is to give Git and Perforce users an uncompromised experience using the version control tool of their choice while still being able to work together seamlessly. The 2013.2 release gets us closer to that goal and, at the same time, makes Git Fusion easier to administrate and use.
Introducing Support for Git Tags
Prior to this release, any tags that were pushed to the Git Fusion service would only be preserved as long as the Git Fusion repository was intact. Now tags of commits are preserved in the Perforce depot, which allows them to be rebuilt if the need arises, as in the case of repopulating the Git Fusion repository. The commit tags can be either annotated or lightweight; both are preserved equally well.
November 04, 2013by Ralf Gronkowski, Product Consultant
What are we using this time?
In the first part of this article I explained why to have a report of all changes not related to an approved review for a given branch in Perforce. Now it is time to implement such a report and we need to get our tooling sorted. For the task at hand we need to query Perforce and Swarm data, and although you could use almost anything, I’m picking Groovy as the scripting language.
October 30, 2013by Murtaza Amiji, Director of Product Management
Distributed teams face unique challenges when they practice Continuous Delivery. For example, it’s critical to keep remote teams up-to-date with the latest code changes within an expected response time—past-due changes can cost the team valuable time and money. Similarly, new features require continuous integration via build and test automation, so that developers can receive immediate feedback, and can rapidly, reliably, and repeatedly launch new features. Network latency and bandwidth, and version management server capacity also become critical bottlenecks for Agile distributed teams, severely impeding Continuous Delivery. These challenges slow down the mainline, the team, and ultimately, the business.Posted In:
October 28, 2013by Bryan Pendleton, Software Engineer
Image: by missresincup w/Flickr
The Perforce server's Spec Depot feature is very handy. If you don't already have a Spec Depot, you should!
It's simple to create one: simply use the 'p4 depot' command to create a new depot, and change "Type: local" to "Type: spec" to specify that your new depot is a Spec Depot.