P4 Blog

  • October 12, 2015

    Has your company had its data or IP stolen yet? It’s possible that it’s already happened, and that you just don’t know about it. Or won’t know until six months from now.

    The theft of corporate IP costs businesses hundreds of billions of dollars per year. Forrester Research recognizes the growing importance of protecting corporate assets from hackers and malicious insiders and has prepared a comprehensive report that outlines how to improve cybersecurity with proper DevOps practices.

  • October 09, 2015

    Perforce on Tour 2015 came to a close at the end of September with the final two stops of our road trip in Berlin and London. The events had an overarching theme of ‘Product Development for Tomorrow’s World,’ and delegates went away armed with great advice and tips to take back to their organizations.

    Posted In:
  • October 08, 2015

    In a previous article I explained how to start a GitSwarm project with a blank repo. But one of the key strengths of GitSwarm is how well it plays with others, and more specifically with the rest of the Helix platform. Today we’ll discuss very briefly how to establish that integration and what it provides.

    Posted In:
  • October 07, 2015

    When we at JetBrains started developing TeamCity—a Continuous Integration (CI) server—about eight years ago, other projects of ours such as IntelliJ IDEA had recently been moved to Perforce. So naturally, the TeamCity project used Perforce right from the start.

  • October 06, 2015

    It’s that time of year when school starts up again, and I don’t know about you, but the thing I like most about this season is the sense of a fresh start. Each new academic year is effectively a blank slate, just waiting to be filled. I’m reminded of that because today it’s my privilege to describe how to create your first GitSwarm project; a new beginning with a blank Git repo waiting for your content.

    Posted In:
  • October 06, 2015

    For the last several weeks we’ve written about the limitations of using Git in larger enterprises, among distributed teams, and within modern release practices. Today we’re excited to say that we’ve done something about it.