October 21, 2016
Sven Erik Knop
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
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.
October 10, 2016
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.
October 04, 2016
In this issue, we’ll consider what it takes to create a fully functioning continuous integration (CI) system, before building a sample project that’s simple, but still designed with the complexity of today’s development burdens in mind. Don’t worry if you’re not a DevOps wizard, it will be easier than you think!
With an eye toward honoring the origins of the DevOps movement, we’ll choose a web application for our sample project.
September 27, 2016
Do You Do DevOps?
DevOps is not one size fits all. I’ve seen organizations apply what seem like universal DevOps axioms only to be deeply disappointed and walk away from the entire project as a result.
Plenty of organizations still depend, sometimes crucially, on complicated legacy applications. You cannot purchase an all-in-one DevOps toolkit and drop a monolithic monster into it for magical results. A multi-million-line, legacy C++ application is different than a web application and requires altering your approach and expectations.
September 19, 2016
The forces of history can act a bit like a pendulum, and this is certainly apparent when it comes to the relationship between development and operations.
The DevOps Disconnect
It isn’t difficult to see where the initial disconnect between developers and operations began. As I explained in a recent webinar, the very nature of the earliest computers mandated it.