DevOps Blog

Lose the Ball and Chain on Your Software Development with Jobs-as-Code

Tina Sturgis
by Tina Sturgis

DevOps is all about increasing the speed of delivering high-quality applications. But many DevOps teams don’t realize how much time they lose because of basic app “plumbing.”

Developers often use simple tools to code basic instrumentation (jobs) as they build apps. The problem is, hardly anyone uses the same tools or adheres to the same standards. The result is a hodge podge of code sitting in the guts of an app. When that app gets passed on to Operations, the cobbled-together code often doesn’t meet production standards. And if something breaks, the problem is hard to find and fix.

The irony is, world-class workflow automation and job scheduling tools have been around for years (take it from us). To avoid rework, headaches and poor quality apps, Dev needs to shift-left these functions from Ops into Dev. We call this approach Jobs-as-Code and believe it’s critical to DevOps success. If you don’t standardize and automate your job definitions, you’re missing a major opportunity to deliver higher-quality apps faster.

Don’t reinvent the wheel

Jobs-as-Code means including jobs as artifacts in your DevOps delivery pipeline. It accelerates the software development process and delivers a higher-quality product operationally.

At BMC, we enable Jobs-as-Code through an API that gives developers access to the powerful app automation in Control-M. Developers can now embed code using a simple notation and manage those job artifacts throughout the continuous delivery pipeline the same way the Java or Python code is managed through the entire software development process today.

Code management systems are the norm for source code and even software-defined infrastructure—so why not for job definitions too? Jobs-as-Code allows job scheduling to have the same standardized, consistent process as the rest of the app components.

Jobs-as-Code means a single interface for job scheduling

With Jobs-as-Code you can improve the job scheduling process. Jobs-as-Code with Control-M:

  • Automates job scheduling
  • Saves time in the delivery pipeline
  • Improves the quality of your apps
  • Ensures visibility so problems that do come up in production are easy to identify and address

The functionality expected in production can now be embedded in the development and test phases using JSON and stored in any SCM, like git. Control-M Automation API provides verification, testing and execution functions exposed as RESTful web services that are easily integrated.

Free your developers to rapidly improve apps and focus on innovation, instead of getting stuck writing scripts. With Jobs-as-Code, Dev can use the powerful and intuitive Control-M functionality to manage workflows, and production doesn’t need to spend time doing rework. The result is high quality, more reliable app delivery at the speed of business.

Speed up DevOps with Jobs-as-Code

Start delivering better-quality applications faster
View the Infographic ›

These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

About the author

Tina Sturgis

Tina Sturgis

Tina Sturgis is currently a Solutions Marketing Director focusing on Control-M Automation API and bringing more Ops into Dev with Jobs-as-Code. With her she brings 20+ years' enterprise software sales, services and marketing experience. Prior to joining BMC in September 2016, Tina spent nearly 13 years at Hewlett Packard Enterprise Software focusing her expertise in project and portfolio management, application lifecycle management and most recently DevOps across the HPE products and services portfolio. Her vast DevOps experience lies in how to implement a DevOps methodology, what a DevOps operating model should look like and how to make DevOps really work inside complex organizations by measuring success and focusing on organizational change. She earned her BBA degree in accounting and economics from the University of Michigan.