Delivery versus deployment

The DevOps team was continuing to onboard their different technology stacks and applications into Harness. They had been making great strides in the process of templating different requirements, enabling and training the other engineers on using Harness, and moving all of the container and serverless applications through a delivery pipeline.

Although the process was moving smoothly, there were some engineers within the company that expressed hesitation with a tool like Harness. Most of the time their concern was related to their lack of familiarity with the tool, or their previous experience of success with a different tool. But, in all cases of concern, a fundamental recurring issue was present: a lack of clarity about what deployment is versus what delivery is. The DevOps team had to go through the same learning process internally, which meant that this lack of clarity came as no surprise to them. But what they needed to decide on was whether they should...