Software impacts our world in many important ways. Almost everything that we touch, from the beginning to the end of our day, relies upon software. Bob Aiello explains the importance of software safety for configuration managers. Remember, software safety requires that systems be built and configured in a secure and reliable way.
Almost any description of a job involving software configuration management—or more generally, application lifecycle management—will include the words “best practices.” Kareen Kircher writes on how to make best practices a reality for your work. The five ingredients to making successful changes happen are relationship, timing, automation, pertinent documentation, and refining.
Environment management is an essential function in any complex, mission-critical system. Unfortunately, environment management is often overlooked and, even when addressed, usually only handled in the simplest way. Keeping an eye on your environment is actually one of the most important functions for IT operations. Bob Aiello explains how to get started with environment management.
Steve Berczuk is a software developer, writer, and experienced practitioner of software configuration management (SCM) and agile software development. He is a co-author of the book Software Configuration Management Patterns: Effective Teamwork, Practical Integration, contributed to the book 97 Things Every Programmer Should Know. Last year, he interviewed Dan Wellman about test-driven development. In this installment of From One Expert to Another, it’s Dan’s turn to interview Steve about the ins and outs of SCM.
The root cause of bad service may have much to do with a personality trait known as anxiety and the often-dysfunctional defense mechanisms people resort to in an attempt to deal with its discomfort. If you want your IT operations group to be successful, then you need to consider the personality issues—at both the individual and group levels—that may impact their performance and your success.
DevOps is more than just a buzzword; it’s about delivering value to customers faster and more reliably. Jonathan Thorpe explains eight mistakes that can dramatically increase cycle time and slow the flow of releases to customers, which is counter to the goals of DevOps.
One of GNU make's many features allows you to shorten build times by running more than one command at a time. If your dependencies are all correct, or nearly correct, this can give you a significant improvement, and since it's built into the tool you get it "for free." But GNU make's parallel build feature—often called "dash j mode," after the command-line option that is used to enable it—is not without drawbacks. The worst of these is that GNU make parallel builds can produce incorrect results if the build dependencies are not sufficiently correct.
The release management system is an important component of the service-transition process. This article highlights the importance of building a monolithic release management system, which encompasses all of the functions and processes necessary to support application build, package, and deployment. The monolithic release management is holistic, comprehensive, and based upon industry best practices. These guidelines are applicable for any type of organization or projects of any size.
While DevOps is typically thought of as being the relationship and interaction between development and operations, the truth is that DevOps impacts QA, testing, and—most importantly—information security (InfoSec). DevOps is, above all else, a set of principles and practices tailored to improve communication between all stakeholders, of which InfoSec is a key part. This article will help you integrate your InfoSec into DevOps.