Scheduled Recurring Deployments RFC

Henrik Andersson discusses the demand for a feature in Octopus Deploy that allows users to schedule recurring deployments, a common functionality in many CI/CD tools but currently achievable only through the Octopus API, which can be cumbersome. The proposed solutions include project triggers and lifecycle triggers, each with its advantages and limitations; project triggers allow specificity per project but require individual configuration, while lifecycle triggers offer shared schedules across projects but are limited to default channels. Users can configure trigger schedules to run daily, weekly, monthly, or at custom intervals using CRON expressions, and can specify actions such as promoting or deploying the latest release, or creating and deploying a new release. The post invites feedback from users to refine these ideas further, encouraging them to share opinions and suggestions, or to follow the open GitHub ticket for ongoing discussion.

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.