April 2016 Summaries

Octopus Deploy is considering the introduction of a new target type called Cloud Regions, which aims to address the challenge of deploying Azure components to multiple regions efficiently. Previously, version 3.0 of Octopus Deploy offered specific deployment targets for Azure, but these were deprecated in version 3.1 in favor of steps. However, the need to deploy the same component across different Azure regions has led to the reconsideration of a target-based approach, as customers have found the current methods—using either separate environments or multiple steps per region—unsatisfactory. Cloud Regions will allow Azure steps to execute multiple times, once for each target, without requiring changes to existing configurations unless desired. This new feature is not limited to Azure and can also be used for executing scripts across different environments, making it useful for various scenarios such as running SQL scripts on both production and disaster-recovery servers. The Octopus team is seeking feedback, especially from users of the deprecated Azure targets, to refine this feature and eventually phase out the old target method.

Octopus Deploy 3.0 introduced first-class support for deploying Azure Web Apps, allowing users to manage environment-specific configurations and promote application releases in a controlled manner. However, deployments can become unreliable, especially for large web apps or when using slow networks. To address this, Octopus Deploy suggests using timestamps instead of checksums for file comparison, which may improve speed and reliability for large applications, though it may lead to false positives. Deploying to a new slot and switching can also enhance reliability by following the blue-green deployment pattern, minimizing downtime. Future plans include upgrading to Microsoft.Web.Deployment.3.6.0, offering better support for JSON configuration files, and addressing issues related to file synchronization using checksums. Users facing persistent issues are encouraged to contact Octopus Deploy's support team for assistance.