Thoughts about DevOps and ALM with Continuous Delivery/h1>

DevOps and ALM -do they both fit into the process of software development

DevOps and ALM appear to be very similar, but still different.  I recently read a blog about DevOps and how ALM fits into the process.  Their argument was that ALM tools, such as source code versioning, is an important part of the process and that there should be a “release vault” where the prod code is stored.  I would agree to some level, but the author was missing an important step.  Source code is not deployed, binaries are deployed the last time I checked.  So just because you have a version control system does not mean that the code that you check into that system can actually compile and execute or that you are actually doing some level of continuous delivery.

The versioning tool should stay on the developer/test/code management side of the house.  A build and a binary repository should be the intermediate steps that connect dev to test or prod.  A build at Test should be executed from the code stored in the source repository against the prod technology stack. The results should be stored in a binary repository for staging to production.

Production control has little use for source code.  Testing should take the source, create the final binaries against the proper prod libraries, test the binaries, store the binaries in a binary repository and mark them for ready to release allowing production control to execute a standard template for deployment.

The author also talked about the use of developer scripts for build and deploy – NO NO NO!!!  If we are to move forward in the DevOps space, we must eliminate one-off script driven processes delivered by every development team.  The redundancy is costly and error-prone scripts are often the cause of many late nights.  As professionals in the “distributed” space, we should get as good as those before us on the mainframe. They dumped private compile and release JCL scripts years ago for improved and automated processors that standardize, streamline and simplify the “DevOps” process on the mainframe  (like 30 years ago).   What is taking us so long to figure that out?  I think on these things often.




Ms. Ragan has had extensive experience in the development and implementation of DevOps for large organizations. She began her consulting career in 1989 on Wall Street specializing in build, testing and release management for the distributed platform. It was during her consulting experiences that Ms. Ragan recognized the lack of standardized development procedures on open systems that were common on the mainframe. In the years leading to the creation of OpenMake Software she worked with development teams in implementing a community driven standardized build and deploy process that enabled frequent builds and releases, automated around version control. Her knowledge and experience contributed to the creation of OpenMake Meister, the first commercial Build Automation solution. Ms. Ragan served on the Eclipse Foundation Board of Directors as an Add-in Provider Representative for 5 years. She has been published on numerous occasions and regularly speaks at conferences including CA World where she presented for 15 consecutive years. She holds a BS Degree in Business Administration, Computer Technology from California State University, Pomona.

Related Posts


Are micro-services and applications independent of each other?

Typically, micro-services are used for the back-end database interactions. For example, user profile micro-service would handle the Create, Retrieval, Update and Deletion of the user profile data. In theory, there should be one micro-service for Read more...


Release Engineer 7.6 with Ansible Galaxy Roles

Ansible Galaxy Roles integrated into Release Management Bridging Ansible Galaxy Roles for Infrastructure Configuration Management with Release Management OpenMake Release Engineer 7.6 inclues the ability to integrate Ansible Galaxy roles into your application release management logic. Read more...


Distributed builds and Configuring Remote Agents

Distributed Builds and Remote Agents Using Distributed Builds with Remote Agents for Continuous Integration Distributed builds requires the use of Remote Agents.  A common question I see on our support forums is how to configure Read more...