March 2014 Summaries

Octopus Deploy 2.4 introduces a range of new features aimed at enhancing user experience, with over 79 issues resolved in this release. Notable additions include step templates for reusing deployment steps across projects, PowerShell modules for script logic reuse, a new Library tab for managing shared settings, and the ability for team memberships to include Active Directory groups. To familiarize users with these updates, a pre-release version is scheduled soon, accompanied by a webinar to demonstrate the features and address questions. The webinar will be conducted twice to accommodate different time zones, and a recording will be made available on the blog.

In a discussion sparked by a query regarding the comparative advantages of Octopus Deploy over Puppet or similar tools, Paul Stovell, the founder of Octopus Deploy, emphasizes that these tools serve different purposes rather than one being inherently superior. While Puppet and Chef are configuration management tools that focus on maintaining a desired system state through automation, Octopus Deploy is a release automation tool that excels in orchestrating ordered deployment steps necessary for application delivery. Stovell suggests that these tools can complement each other effectively: Puppet can be used for provisioning infrastructure and maintaining system readiness, while Octopus is better suited for the continuous delivery and updating of applications. This integrated approach can accommodate the specific needs of both development teams and system administrators, leveraging each tool's strengths for optimal productivity.

Paul Stovell discusses the complexities of prioritizing feature requests for software development at Octopus Deploy, highlighting that decisions should not be based solely on user votes. He outlines a framework for evaluating requests, considering factors such as the number of votes, the feasibility of workarounds, implementation difficulty, and ongoing support costs. Stovell uses three specific feature requests from the Octopus Deploy UserVoice site to illustrate his point: scheduling deployments, selecting multiple environments for deployment, and supporting Internet Explorer 8. He argues that while "Scheduled deployments" and "Multiple environments" are equally feasible, the less ideal workaround for the former makes it a higher priority despite having fewer votes. In contrast, he declines IE8 support due to its high ongoing costs and dwindling market share, emphasizing that sometimes features with higher votes may still be impractical to implement. Stovell concludes by inviting feedback on whether popularity should be the main factor in prioritizing features.

Paul Stovell, the founder of Octopus Deploy, introduced a Live Demo server to provide users with a hands-on experience of how Octopus Deploy operates. This demo server, which features the latest version of Octopus, allows users to sign in as a guest and explore the system in a read-only mode, providing insight into its functionality without the ability to make changes. It includes two projects deployed to seven Tentacles and is integrated with a demo TeamCity server that automatically compiles code and deploys it to Octopus every hour, while also promoting releases weekly. The demo showcases features like rolling web application deployment, library variable sets, and Windows Service configuration, serving as a useful reference for understanding Octopus Deploy's capabilities.

Octopus Deploy 2.3 introduces several enhancements aimed at improving deployment processes and user experience. Key updates include the ability to prompt for variables at deployment time, allowing users to input values or use defaults, with options for sensitivity and scoping. Users can now deploy to specific machines without affecting others in the environment, and the task output has been enhanced with an "Interesting" mode that expands relevant log nodes automatically. Audit logs can now be filtered by person, project, or date range, and custom expressions in package IDs and feeds simplify workflows across different environments. The release also addresses task cancellation, now allowing the termination of hanging PowerShell processes, and improves dashboard and task output performance to handle larger volumes of data more efficiently.