P4 Blog

  • November 29, 2016



    DevOps Digest 303 Learning About Streams

    In DevOps Digest 203 we compared promotion and trunk-based branching strategies, concluding that trunk-based development (TBD) grants us the most freedom and flexibility for rapid release cycles. Today, we take things further and explore the ways streams, a feature unique to Perforce Helix, can help us implement our strategy.  

    Streams are a way to codify TBD best practices, ensuring that only the most stable code flows upward, while developers can create any number of streams and child streams to organize teams in whatever ways make sense.

    Posted In:
  • November 17, 2016

    “We have developers all over the world, including many contractors. Perforce [Helix] allows us to define very granular access to the game, resulting in faster turnaround and better control.”

    Paul Vaden, Network Services Manager, Cloud Imperium Games


    Posted In:
  • November 15, 2016

    DevOps Digest Issue 302 image

    Now that the build process works nicely in Jenkins, our next step is automating it, but this requires some thought. It’s easy enough to establish simple source control polling to execute our current job whenever Jenkins detects changes in Perforce Helix. We could even make it event driven by establishing a trigger on the Perforce Helix server to launch the build in Jenkins.

    But what do we really want to build automatically?

    Posted In:
  • November 08, 2016

    DevOps Digest 301 Image

    In Issue 205, our Jenkins project built our sample project, the first major step on our DevOps journey. But plenty more remains to be done as we enter Chapter 3 and take a closer look at continuous integration to start reaping more significant benefits from our work.

    Posted In:
  • October 31, 2016

    In last week’s issue,DevOps Digest 204: Configuring for Build Automation with Jenkins, we gave you pointers to avoid the extra headaches and to streamline your Jenkins configuration.

    We have gradually built momentum for this final burst to establish the pipeline to build our sample application and to set up a basic, build-per-commit continuous integration process in Jenkins.

    Posted In:
  • October 24, 2016

    DevOps Digest Issue 204 Graphic

    After creating our sample application last week and getting it stored in our version control platform, Perforce Helix, we’re finally ready to create a Jenkins project to build it every time we submit a change into the mainline. The challenges we overcome should provide a solid foundation for discussing more advanced CI topics later. But this week, we’ll demonstrate common problems and pitfalls when configuring projects in Jenkins so that you’re better equipped to handle them.

    Posted In: