October 2012 Summaries

ReadyRoll is a Visual Studio project system designed to simplify the creation and management of migration scripts for SQL Server databases, particularly in continuous delivery environments. It distinguishes itself from other SQL deployment tools by its focus on change scripts and seamless integration with Octopus Deploy, an automated release management tool for .NET. Paul Stovell, the founder and CEO of Octopus, highlights the synergy between ReadyRoll and Octopus, as both tools support the continuous delivery principle of "build once, deploy many times," ensuring consistency of build artifacts from development through to production. Stovell, who also enjoys carpentry and DIY projects, emphasizes ReadyRoll's capability to enhance SQL Server database deployment when used alongside Octopus Deploy.

On October 30, 2012, Paul Stovell announced a new update to Octopus Deploy, which primarily addressed minor bugs from the previous 1.1 release but also introduced a significant feature enhancing security and management. The update allows users to control variable viewing and editing permissions at an environment level, which is illustrated by restricting access to production environment variables in the Columbia project. This feature is designed to ensure that sensitive production settings and passwords remain secure by limiting access to authorized groups, such as a "devops" team, while denying it to others. The addition aims to streamline the management of production environments within organizations, enhancing trust and security in Octopus Deploy.

The upcoming version of Octopus will introduce retention policies to manage the number of releases and deployments retained, optimizing disk space usage and enhancing performance. These policies will integrate with the Project Groups feature, allowing configuration across similar projects without redundancy, and will determine when Release, Deployment, and Task objects are removed from the RavenDB database. The policy settings cater to various scenarios, such as deleting unused releases after a week or retaining deployed releases longer. Tentacles will have a setting based on the number of deployments to manage extracted package folders, avoiding the need for scheduled cleanup jobs. Additionally, NuGet packages will automatically be cleaned every 12 hours for packages older than three days, with re-downloads facilitated through the NuGet server. Feedback is sought to ensure the feature remains powerful yet simple, and input on whether project groups are the appropriate level for defining retention policies is requested.

Octopus Deploy version 1.1 introduces significant updates, including the innovative use of machine roles, which allow machines to be tagged with specific roles rather than being tied directly to environments, enhancing flexibility in deployment processes. This update simplifies the management of machines and variables, enabling easier transitions between environments and more efficient scoping of variables. The release also introduces project groups, allowing projects to be organized for better management and future integration of retention policies and permissions, thus streamlining the dashboard layout. Additionally, a new "favorites" feature has been added for personalized navigation, allowing users to control which projects appear in their menu. These changes necessitate updates to the data model, urging users to back up their data before upgrading, as the release also includes a new version of Octo.exe to support these enhancements.

ioGlobal, an Australian company specializing in applied geochemistry and resource analytics, began using Octopus Deploy in May for deploying their web applications, including ASP.NET WebForms and MVC, as well as services based on OpenRasta and NServiceBus. Stacy Andrews, the CTO of ioGlobal, shared insights on their deployment environments, which include multiple testing environments, a staging environment hosted by RackSpace, production environments in Australia and North America, and a disaster recovery setup with Amazon Web Services. Before Octopus Deploy, deployments were manually handled via PowerShell scripts, which was cumbersome and mixed deployment concerns with build scripts. Andrews highlighted Octopus Deploy's strengths, such as its simplicity and reliance on common technologies, while noting some UI workflow confusion and the lack of built-in continuous deployment tools. He advised those new to automated deployment to adopt Octopus Deploy gradually, starting with web applications and utilizing the comprehensive documentation provided.