November 2012 Summaries

Paul Stovell discusses the introduction of manual deployment steps in Octopus, a feature designed to address situations where human intervention is necessary during the deployment process. While automated deployment is ideal, certain tasks—such as obtaining approvals, verifying site functionality, or performing database upgrades—require manual handling. The new manual step feature allows users to define instructions and assign them to specific user groups, like managers, who must approve or cancel the deployment during a paused state. Feedback is encouraged, with suggestions like sending email notifications to approval groups being considered. This development aims to improve flexibility and control in deployment scenarios where automation is not feasible.

Paul Stovell discusses the communication model of Octopus Deploy, which uses a standard client/server approach where the Tentacle listens for connections from the Octopus server. He addresses a common feature request to reverse this model, allowing Tentacles to initiate connections to the server, which could potentially bypass firewall restrictions. However, Stovell argues against this reversal, noting that it could undermine trust with system administrators by circumventing established firewall rules. He suggests that while there might be valid scenarios for reversing the communication model, such as deploying desktop software or dealing with slow firewall rule changes, these cases are exceptions rather than the norm. Stovell emphasizes that the current architecture aligns with traditional operations tools and maintains simplicity, suggesting that altering it could create distrust in the product. Despite potential scenarios that might benefit from a reversed model, he concludes that the implementation effort and potential trust issues do not make it a high-priority feature.