Octopus Deploy 3.6 - Project Trigger enhancements

Octopus Deploy 3.6 introduces a new versioning strategy aimed at releasing minor versions as soon as features are ready, rather than bundling them, to minimize upgrade friction and expedite the delivery of new functionalities and bug fixes. This release includes significant changes to Project Triggers, allowing users to select any machine-related event to trigger automatic deployments, thereby providing more flexibility and predictability. The update simplifies the machine selection logic by eliminating complex calculations and aligning event filters with those shown on the Configuration > Audit screen. Additionally, the release includes a schema change affecting Project Triggers, requiring a database backup to revert to an earlier version. Looking forward, Octopus Deploy plans to expand Project Triggers by incorporating more events and actions, such as deploying projects based on the success of other deployments or triggering releases when packages are pushed.

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.