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.
October 23, 2013How to Version Character Sets: Solving the Problem of Having Multiple Files with Multiple Different Charsetsby Sam Stafford, Developer at Perforce Software
The functionality described in this blog entry is "undocumented", meaning that it is in some respects a work in progress, is subject to change in future releases, and should be treated with a bit more caution than "documented" functionality. With that disclaimer out of the way, let's take a look at how you can now version the character sets for individual Unicode files!
October 21, 2013
by Natalie Estrada, Marketing Events Manager
Collaboration Tour: Git, Global, Social
Join us on the road in November for a series of half-day seminars to learn how leading organizations are releasing better products faster and collaborating globally by making better use of their version management platform.Posted In:
October 18, 2013by Nellie LeMonier (@p4nellie), User Experience Designer
Swarm is designed to help software teams ship quality software faster and every day we add new, useful functionality. We recently got many requests to further enhance our JIRA integration and so we added a couple of enhancements which make life a whole lot better for those using both JIRA and Swarm.
October 17, 2013by Sven Erik Knop, Technical Marketing Engineer
A typical use case for a P4 script is to process some or all spec objects such as client workspaces, labels or changes. For example, I might want to change the options of all existing client workspaces from normdir to rmdir. The workflow would then be:Posted In: