Packages in Script Steps

Michael Richardson discusses new enhancements in Octopus Deploy, specifically the ability to reference multiple packages, including container images, in script steps. Previously, users could only reference a single package that contained the script to be run, but now they can also reference packages that do not contain the script, which facilitates more flexible interactions with files and metadata. This update addresses the limitations of the previous "wrapper" package and "deploy-the-packages-first" patterns, making deployment processes less complicated and more versatile. The integration of container images allows users to capture image versions at release creation, and these can be acquired on execution targets or not at all, optimizing resource use. Using an example from Octopus HQ, Richardson illustrates how the enhancements simplify the deployment process by allowing packages to be extracted or left un-extracted as needed, and how variables from package references can be used effectively in custom scripts. Additionally, the update includes file variable-substitution features, further enhancing the flexibility and functionality of script steps within Octopus Deploy.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.