Chapter 1. Deploy
The deploy stage (see Figure 1-1) represents taking code that has been developed and packaged and shipping it to a destination for user consumption. It’s the result of local development becoming shippable code. Development teams value code that’s been shipped to the dev environment—but ultimately the organizational value is still low. As code gets closer and closer to production environments—where end users can consume and interact with it—the value (and ultimately the risk) increases.
Figure 1-1. The deploy stage
One of the most outdated aspects of the DevOps infinity loop is that release precedes deploy. This sequencing can be traced back to the idea that once a build of software code was “development complete” (i.e., all development on specific changes was done), the code would be released into the build processes. This definition not only no longer holds true but also is too restrictive for the speed and scale at which teams need to build and ship their software. It’s also worth noting that in this context, we’re using release to refer to the activity of releasing software and not to the actual version of a software release.
In modern software development, the deployment process covers the workflow of moving compiled code onto a destination infrastructure or software platform. While this is roughly reflected in the infinity loop chart, the methods of facilitating ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access