P4 Blog

  • 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:
  • October 21, 2016

    P4Python and the Python logging API

    Many of the P4Python scripts I have encountered (and written myself) are simple triggers or little utilities that typically do not require logging. Occasionally, though, some of these scripts become complex projects performing a multitude of functions and invoking many different Perforce commands. Debugging these scripts and performing any kind of post-mortem in case of a failure then becomes a challenge. Logging has been provided to address these challenges.


    Python has an impressive logging API that has been described elsewhere, so I just want to highlight the bits I need for this post.


    For example:


    Posted In:
  • October 10, 2016

    DevOps Digest 203 Graphic

    Last week in DevOps Digest 202, we made sure failure would NOT be an option, by setting up your development environment with the right tools, such as Visual Studio and Jenkins, for DevOps success.

    With all the work we’ve done, it’s time to do some actual coding and start seeing some payoff. So let’s create a new application and get the source code under version control.

    Posted In:
  • October 10, 2016

    Graphic for DevOps Digest 202

    It’s time for us to start setting up. We need to provision some hardware to receive the software essential to building out our DevOps pipeline. We’ve created a single, virtual machine (VM) with Windows 2012 Server. Its network name is DevOps with a single user named Perforce.

    Posted In: