January 28, 2014by Bob Dever, Director of Corporate Marketing at PerforcePosted In:
January 24, 2014by Furkan Khan, Director of Product Management
We are excited to announce new Perforce collaboration features for you this month. Here is a summary of updates you can download from our website immediately.
- Perforce Git Fusion 2013.3: Git with Perforce for enterprise Git management
- Perforce Commons 2013.6: Document collaboration syncs with Dropbox
- Perforce Insights 2013.3: Easier data integration for Perforce analytics
January 23, 2014by Alan Teague, Chief Architect at Perforce Software
Git Fusion 13.3 is now on the web and ftp site. Among a small collection of bug fixes are 3 really cool new features: support for Git submodule, support for stream-based Git repos, and fine-grained read-access control for Git repositories.Posted In:
January 21, 2014Matt Attaway, Open Source Community Manager (@p4mataway)
January 17, 2014by Matt Attaway, Open Source Community Manager (@p4mataway)
If you've played with Perforce's new asset collaboration tool Swarm you've probably seen that making links to Perforce data in Swarm is way easier than it is in P4Web. Just take your Swarm hostname and attach the thing you're interested to the end of your URL and you're set.
Swarm is also Git savvy though if you are using Git Fusion as well. You can just as easily tack on the first 8 characters of a SHA from a Git commit stored in Git Fusion to view the same commit in Swarm.
January 15, 2014by Jackie Garcia, Senior Solutions Engineer at Perforce Software
During a Streams demo with a customer, many questions came up about unshelving into a different stream/branch. Our Shelving feature has been a part of our product since 2009.2, and the unshelving into a different branch feature was released in the 2013.1 version of the server.
When unshelving into a different branch, you need to consider the stream relationship. The key to dealing with unshelving into another branch is to not specify directionality for the actual unshelve, but rather specify to get the appropriate branchview to move the files, which is always generated by the child to parent relationship. Another key consideration is that there must be a direct relationship of the unshelved files example: