Skip to main content

Removing Anxiety from Your Software Delivery Process with Armory Spinnaker

“What does your CI/CD process look like?” This is the question that Armory CTO Isaac Mosquera asks at every client meeting. It’s rare to find organizations that have a holistic view of their entire software delivery pipeline. The more common scenario has several teams owning portions of the pipeline, and responsibility is distributed across the organization. With so many approvals, stakeholders and steps involved, it is little wonder that organizations look at software delivery with anxiety. Isaac recently gave a talk at DeliveryConf 2020 in Seattle, Washington where he goes into Armory’s process for identifying and improving pain points in your software delivery process. Take a look here:

Main Takeaways

  • Workshop your current delivery process with engineers and leaders of all levels in your organization
  • Have everyone contribute their view of what the process looks like (it helps to use sticky notes and a whiteboard so you can iterate quickly)
  • Construct a shared model from these viewpoints
  • Identify gaps, pain points, and other misses in your current process
  • Leverage Spinnaker to augment your current delivery process by:
    • Using Spinnaker’s Jenkins integration to build off of what you have
    • Add manual handoffs to facilitate humans in the loop
    • Use automated deployment verification (both during and post deploy)
    • Visualize your applications and infrastructure at every stage of the process

What to do from here:

If you’d like to improve your organization’s ability to digitally transform, we recommend starting with a workshop, as described in this post:

“An Interactive Workshop: Bridging the Gap Between Digital & Cultural Transformation

Just contact us and we will schedule that session with you.

If you like this post, you might also like: