June 2019 Summaries

Shawn Sesna outlines an efficient method for populating Octopus Deploy project variables by leveraging PowerShell scripts and the Octopus Deploy API to import Environment variables from the SSISDB, thereby resolving the manual and time-consuming process of creating variables individually. The strategy requires that the SSIS package is deployed at least once to ensure Environment variables are populated in the SSISDB. This approach, though exemplified specifically for SSISDB, can be applied broadly to various sources, showcasing how automation can streamline workflows and satisfy developer demands for efficiency.

Shane Gill reflects on his fifth anniversary at Octopus and his experience with the company's computer policy, which allows employees to upgrade their hardware every few years. Throughout his career at Octopus, Gill has transitioned from using a MSI WS60 laptop, balancing power and portability, to a more powerful but less portable Metabox Prime laptop to accommodate remote work and performance investigations. For his anniversary, he built a custom desktop, Octobox-V, designed to be a powerful yet silent code compiling workstation, featuring a Ryzen 7 2700X, 32GB DDR4 3200, RTX 2070, and a combination of PCIe and SATA storage. This setup significantly reduced compile times by 65% and eliminated fan noise, while still allowing him to play StarCraft, a game he admired since his youth. For remote work, he uses an ultrabook to connect to Octobox-V via VPN, achieving both performance and portability without compromise.

Shawn Sesna's blog post explores the integration of PowerShell Desired State Configuration (DSC) with Octopus Deploy for managing Windows-based servers, focusing on creating a dynamic and reusable deployment process. It begins by demonstrating how to separate Node data into a configuration data file, making the DSC script more adaptable. The post outlines how to convert a basic DSC script into a step template within Octopus Deploy, allowing for automatic server configuration, monitoring for drift, and marking servers as unhealthy if discrepancies arise. It emphasizes the use of variable substitution for customizing deployments across different environments and projects. Additionally, the post highlights the necessity of including specific DSC resource modules, like xWebAdministration, and suggests managing these modules and configuration files as deployable packages stored in source control. By the end, it illustrates a comprehensive approach to deploying and monitoring server configurations, akin to application deployment, with a focus on flexibility and automation.

In episodes 28 to 30 of the "Ask Octopus" series, the discussions focus on practical tips and updates for managing Octopus servers and configurations. Key topics include substituting Boolean and number values into JSON configuration files, treating Octopus servers with a cattle-not-pet approach, and addressing recent changes in Active Directory that may impact users. Viewers can access previous episodes and submit questions on the Ask Octopus page, while additional information about these topics is available in their documentation. The series encourages viewers to subscribe to their YouTube channel for updates on new episodes.

In a series of episodes from "Ask Octopus," topics such as configuring Centralized Logging for Octopus, viewing the worker working directory contents, and integrating Octopus with TeamCity are discussed. These episodes, featuring insights from Bob and Derek, aim to provide users with practical guidance on these technical aspects. Viewers can access previous episodes and submit questions via the Ask Octopus page, while further information on discussed topics is available in related documentation and webinars. The content encourages engagement through YouTube subscriptions and playlist following to stay updated on new episodes.