InfoQ Homepage ALM Content on InfoQ
-
CFEngine's Decentralized Approach to Configuration Management
Mark Burgess and Diego Zamboni introduce CFEngine. They describe the challenges regarding web scale - scale, complexity and knowledge - and how CFEngine helps to tackle those challenges with a fundamentally decentralized and knowledge-oriented approach. An example demonstrates how those ideas translate into practice.
-
The Top Automation Tools for Public Cloud at Scale
As more organizations expand their use of public cloud services, from early-stage startups to the biggest businesses and governments in the world, the problems of cloud computing at scale start to arise.
-
Purely Functional Configuration Management with Nix and NixOS
This article gives a short introduction to NixOS, a Linux distribution, and to Nix, the package manager on which NixOS is based. These provide a declarative approach to configuration management with many advantages to users, such as strong reproducibility and atomic upgrades and rollbacks.
-
Ansible’s View on IT Automation
Michael DeHaan, creator of Ansible, introduces the general-purpose IT automation system. He describes the tool’s guiding principles: simplicity, ease of use and maximum security. The philosophy behind its community is also discussed, including the importance of Ansible’s plugin-based model. Michael uses a simple but common scenario to demonstrate Ansible.
-
Exploring the ENTIRE DevOps Toolchain for (Cloud) Teams
When assessing technology that empowers a DevOps transformation, it’s easy to focus in on the headline capabilities (“configuration management!”) and miss out on the bigger picture. How can teams shipping cloud (or on-premises) applications use the full suite of DevOps technologies to simplify delivery and management at scale? This article classifies and explains key enabling technologies.
-
Towards Agile CMMI Level 3: Requirement Development and Verification
This article shows how to do requirement development in agile environments, covering concepts and offering examples of how an agile team could run a CMMI for Development SCAMPI to become appraised at a targeted level 3 for the areas of requirements development and verification.
-
Interview and Book Review of The Technical and Social History of Software Engineering
Capers Jones wrote the book The Technical and Social History of Software Engineering in which he provides an overview of the evolution of information technology and software development. InfoQ interviewed Capers about advancements and events in software engineering and the effects that they have had on our society.
-
DevOps @ large investment bank
This article is part of the “DevOps War Stories” series. In each issue we hear what DevOps brings to a different organisation, we learn what worked and what didn’t, and chart the challenges faced during adoption. This time a very personal story on introducing a DevOps mindset at a large bank. In particular how the automation of configuration and release management processes enabled collaboration.
-
Implementing Software Lifecycle Integration (Part Two)
In this article we focus on the practical steps a software delivery professional should take in implementing an end-to-end software delivery process. The three basic steps are prioritizing needs, team building, and measuring results.
-
Book Review: Vagrant up and running
Mitchell Hashimoto released his book "Vagrant up and running" which covers everything from basic Vagrant usage to extending its functionality. In seven chapters he explains every aspect of Vagrant - from staring a default VM to extending it via plug-ins.
-
The Case for Software Lifecycle Integration
For many years, software delivery has been treated as an ancillary business process; a business process that, though costing the organization a considerable amount of money, does not have the structure, rigor, or focus of other enterprise business processes such as supply chain management, financial management, and even talent management.
-
Managing Build Jobs for Continuous Delivery
The number of jobs in a continuous integration tool can range from a few to several thousand, all performing various functions. There is an approach to manage these jobs in a more efficient manner.