Part 4 of a 5-part series on building an Internal Developer Platform with Octopus Deploy. Covers structuring deployment projects to support a shared responsibility model, where multiple teams (platform and security) own different stages of the deployment process using process templates arranged in an 'onion' pattern. Explains how pre/post-deploy hook templates allow each team to maintain their portion of the pipeline, and connects this to Conway's Law. Also touches on Git-based workflows and SemVer for managing process templates at scale.
Sort: