P4 Blog

  • July 13, 2015
    When starting a complex project, it's wise to verify you aren't re-inventing the wheel. With the wealth of available open source projects it's likely there are useful components (be they libraries, a web server, etc.) or if you're particularly lucky, a product that is close to what you need.

    Posted In:
  • July 07, 2015

    We’ve built a lot of different tools for our users over the years, but two of the most popular have been P4Java, our pure Java API for Helix, and P4Eclipse, our native IDE integration. Given our focus on enterprise-grade version control, it’s not entirely shocking that we have a lot of users working in Java and other JVM-powered languages. These two tools have been a big win for our Java using community.

    Posted In:
  • July 06, 2015

    I recently did a DevTalk introducing the new distributed version control system, or DVCS, features we’ve added to Perforce Helix. If you missed the DevTalk, you can see our new features in action by watching the on-demand version. I got a number of really good questions at the end of these talks, so I thought I’d take the opportunity to provide some more detailed answers here.

    Posted In:
  • July 02, 2015
    Perforce’s own Chris Hoover and Charlie McLouth recently hosted a webinar called ”Learn How to Stop Data Theft Before It Happens,” which gave a great overview of the features and advantages of our Helix Threat Detection capabilities.  As you might guess from the title of the webinar, Helix Threat Detection…
    • Detects anomalous user behavior against the assets stored in Helix repositories. 
    • Eliminates false positives by using advanced math models and machine learning to categorize high-risk users and projects. 
    • Detects internal theft and compromised accounts early enough in the process that you can respond before harm has been done.

    Posted In:
  • June 30, 2015
    With POODLE, Heartbleed and other vulnerabilities in the news, I’ve had many of my customers asking me about the cryptographic protocols used in Perforce Helix. SSL 3.0 is used by many legacy systems and is vulnerable to attacks. However, our Helix Versioning Engine (P4D) does not use SSL 3.0 and supports only TLS 1.1.

    Posted In:
  • June 29, 2015
    In the 2015.1 Perforce Helix release, engineering improved the performance of two distributed version control system (DVCS) commands: p4 status and p4 reconcile (aka p4 rec). The p4 reconcile and p4 status commands were first introduced in the 2012.1 release of Helix. These commands do a recursive scan of your local workspace files, comparing the Md5 checksum of the actual files in your workspace to the checksum stored in the p4d server. Using the results of this scan, p4 decides if files have been added, modified or deleted in the workspace, and marks them for add, edit, or delete as appropriate. It will also figure out if you’ve moved files, even if you’ve made small changes as can happened with refactored Java files.