👉 AWS Debug Games (Beta) - Prove your AWS expertise by solving tricky challenges.

👉 AWS Debug Games - Prove your AWS expertise.

Process-as-Code #c9d9

Michael Wittig – 24 Aug 2016

DevOps at scale requires predictability and consistency. Your application code is versioned. Infrastructure-as-code defines your environments. But what about the process?

On Tuesday I participated in an online panel on the subject of Process-as-Code, as part of Continuous Discussions (#c9d9), a series of community panels about Agile, Continuous Delivery and DevOps.

Watch a recording of the panel:

Continuous Discussions is a community initiative by Electric Cloud, which powers Continuous Delivery at businesses like SpaceX, Cisco, GE and E*TRADE by automating their build, test and deployment processes.


Looking for a new challenge?

  • DEMICON

    Cloud Operations Lead

    DEMICON • AWS Advanced Consulting Partner • Remote (Europe)
    service-delivery-management hiring devops platform

Below are a few insights from my contribution to the panel:

What is Process-as-Code

Let me use Jenkins and a software delivery pipeline as an example:

  • At the beginning, only the source code was version controlled. Jenkins contained all the information that was needed to build, test and deploy the application.
  • Then we moved the build, test, and deploy scripts into version control and Jenkins only contained the information about what scripts to execute in which order.
  • Now we put the whole pipeline under version control, and Jenkins only knows where to get the process configuration from to execute it.

So process as code is two things: a description of the process and a runtime environment that can execute that description.

Best Practices

  • Idempotent process steps that can run asynchronously and can be retried.
  • Having a descriptive language for your process and let an execution engine figures out how to execute the process description.
  • We use a lot of Amazon tooling: CloudFormation, Code Pipeline, and Lambda.

Become a cloudonaut supporter

Michael Wittig

Michael Wittig ( Email Twitter LinkedIn Mastodon )

We launched the cloudonaut blog in 2015. Since then, we have published 365 articles, 67 podcast episodes, and 67 videos. It's all free and means a lot of work in our spare time. We enjoy sharing our AWS knowledge with you.

Please support us

Have you learned something new by reading, listening, or watching our content? With your help, we can spend enough time to keep publishing great content in the future. Learn more

$
Amount must be a multriply of 5. E.g, 5, 10, 15.

Thanks to Alan Leech, Alex DeBrie, Christopher Hipwell, e9e4e5f0faef, Jason Yorty, Jeff Finley, jhoadley, Johannes Konings, John Culkin, Jonathan Deamer, Juraj Martinka, Ken Snyder, Markus Ellers, Oriol Rodriguez, Ross Mohan, sam onaga, Satyendra Sharma, Simon Devlin, Todd Valentine, Victor Grenu, and all anonymous supporters for your help! We also want to thank all supporters who purchased a cloudonaut t-shirt.