P4 Blog

  • January 25, 2017

    Perforce Natively Integrates with Amazon Lumberyard for Game Dev_Image

    Cloud computing has spilled a lot of virtual ink in its first decade. It seems like every week there’s some new announcement about moving data to the cloud, applications to the cloud, even entire infrastructures to the cloud. Perhaps it should come as no surprise then that game development and multiplayer gaming in particular are heading that way as well.

  • January 24, 2017

    A few years ago, I posted a blog article on how you can add colors to the P4 command line. This involved a lot of hacking, administrator access and a specialised P4 executable for Windows to work, as well as a modified journal file. Not for the faint of heart or, as the post stated: Here be dragons.

    Posted In:
  • January 19, 2017

    Introduction

    Today I’m writing in response to a recent article entitled “Splunk: Why we dumped Perforce for Atlassian’s Bitbucket of Gits”, primarily because it offers a great opportunity to correct a variety of misconceptions regarding Perforce Helix. The TLDR version is that the article contains several factual inaccuracies, and Splunk’s main complaint about Helix is simply no longer valid.

    Posted In:
  • January 19, 2017

    In gaming, where development teams vary in size, scope, and direction, version control platforms must cater to wildly disparate operations. Because whether the game being constructed is a once-in-a-generation title or an in-house release from an independent studio, the change management and file versioning must be ironclad. 

    Posted In:
  • January 16, 2017

    DevOps Hero Image

    In Issue 307 we got basic, extensible unit tests working, making it easy to add new tests and unit-test assemblies to the project over time. Our use of build scripting made it possible to add that functionality and leverage it in Jenkins with very little effort, importing test results and associating them with each build.

    Posted In:
  • January 10, 2017

    After Issue 306, our basic build scripting tools work. With our NAnt-powered framework in place, let’s extend our continuous delivery pipeline with targets that execute unit tests. It’s nice to have a continuous integration system running a debug build in response to every commit, but all success tells you is that the code compiles. A more interesting measure of quality is whether all the unit tests pass when executed.

    Toward that end, we will:

    Posted In:

Pages