May 2014 Summaries

Paul Stovell addresses a common issue in software deployment where locked files can obstruct the process, leading to frustration and the need for a solution to identify and stop processes locking those files. The article introduces Handle, a utility from SysInternals, which provides a way to find out which programs have specific files open, thus helping to resolve these deployment issues. By using Handle, users can pinpoint the exact processes causing file locks and terminate them using a PowerShell script, facilitating smoother deployments. Additionally, Stovell highlights a possible complication with Handle's End User License Agreement (EULA), explaining that it must be accepted per-user, which can be automated to prevent issues when running Handle from the Octopus Deploy Tentacle agent.

Octopus 2.4 introduces a feature that allows variables from one deployment step to be available in subsequent steps, enhancing the flexibility and efficiency of deployment processes. This is accomplished through output variables, which can be created using the `Set-OctopusVariable` command and are stored after each step for later use. In addition to user-defined variables, Octopus provides built-in output variables for tasks like NuGet package deployments and manual interventions, offering details such as installation directory paths and user information. The system operates across multiple machines simultaneously, meaning each machine can produce different values for the same output variable, which are then scoped to individual machines. For broader access, Octopus also indexes variables by machine, allowing steps running on different machines to retrieve values produced elsewhere. This functionality is particularly useful for tasks like determining previous package installation paths, as Octopus extracts packages to new directories by default to prevent issues. The integration of output variables streamlines the deployment process by facilitating the sharing of values across steps and machines, making it a powerful tool for managing complex deployments in Octopus.

Octo.exe, a command-line tool for automating Octopus Deploy, has introduced two new commands, export and import, designed to facilitate the synchronization of projects and releases between multiple Octopus Deploy servers in different locations. This development addresses the previous need for manually recreating projects and releases on separate servers, enhancing efficiency in environments where one server is used for initial setup and testing before transferring to a production server. The export command enables users to save project and release data into a JSON file, while the import command requires certain prerequisites, such as existing project groups and environments, to successfully integrate these exports into another server. Sensitive variables are not exported, necessitating updates through the UI. This tool is versatile and open-source, allowing for modifications to suit specific needs, making it useful for migrating projects and releases across different Octopus servers.

Octopus 2.4 introduces a new feature allowing users to create reusable deployment steps that can be shared between projects, enhancing the flexibility and capability of the product without requiring changes to its core. This update includes the launch of a Library website, a GitHub repository where users can find, import, and contribute step templates, such as installing Chocolatey packages or pushing to Azure. The initiative encourages community involvement by offering a competition where contributors can win an Octopus Deploy mug for submitting accepted step templates. This collaborative approach aims to build a comprehensive resource for common Windows/.NET deployment tasks, promoting a culture of sharing and innovation within the Octopus user community.

In a guest post by Jonathan Goldman on Paul Stovell's blog, the need for sharing deployment scripts across multiple projects in Octopus Deploy is addressed by utilizing a library of PowerShell scripts. To avoid the inefficiencies of copying and pasting scripts, Goldman developed an internal NuGet package containing deploy scripts, including an Init.ps1 step for copying them to a solution folder. This allows projects to easily reference the scripts, and updates to scripts can be managed via the update-package command. Recognizing the generic nature of many scripts, Goldman created a public NuGet package, BuildDeploySupport, to further streamline deployment tasks such as installing services, configuring app pools, and setting up websites directly within the deployment process. This approach not only simplifies deployment but also encourages community collaboration, with the project being open-source and available on GitHub.

Paul Stovell, the founder and CEO of Octopus, announced improvements to their internal development and release processes, including the publication of builds for Octopus and its related tools to various platforms. These include the official downloads page, Chocolatey packages for the Octopus server, Tentacle agent, Octo.exe, and NuGet.org packages for Octo.exe and Octopus.Client. The Chocolatey packages for Octopus server and Tentacle download the MSI files and install them silently, allowing for automated configuration via the command line. Additionally, the Octo.exe Chocolatey package adds the executable to the system path, facilitating quick access and execution. Paul, who founded Octopus with his wife Sonia in 2012, enjoys carpentry and DIY in his spare time.

Paul Stovell, founder of Octopus, shares his experience managing an overwhelming backlog of feature requests and issues, highlighting the challenges of maintaining a large number of suggestions in GitHub. He describes the process of streamlining the backlog by separating tasks into those that will definitely be completed soon and those that are merely suggestions, which are now moved to UserVoice—a platform where users can vote on ideas, giving the company a clearer picture of what is important. Stovell emphasizes the importance of balancing customer suggestions with the company's long-term vision, and he outlines a strategy that includes regular releases with a mix of bug fixes, community input, and planned roadmap items. He also mentions the company's growth and hiring needs, encouraging talented .NET developers to join their team.

Paul Stovell, the founder and CEO of Octopus Deploy, announced a webinar detailing the upcoming features in Octopus Deploy 2.4, including step templates, PowerShell modules, and Active Directory group support. The webinar aimed to inform users about the new release and engage them with a Q&A session. For those who missed the live event, a recording was made available. Stovell, who started Octopus with his wife Sonia in 2012, also enjoys carpentry and DIY projects in his spare time.