May 2021 Summaries

Octopus Deploy's 2021 Q2 release enhances the cloud experience with features like self-service project migration to Octopus Cloud, improved integration with GitHub Actions and HashiCorp's Terraform, and new deployment capabilities for Azure App Service. The release supports better scalability by allowing more concurrent automation tasks and increased storage capacity, while also offering improvements to the Tentacle agent configuration without requiring root permissions. A significant change includes the deprecation of Windows Docker images for Octopus Server and CLI due to low uptake and unsupported OS versions, urging users to switch to Linux Docker images. The release emphasizes Octopus's commitment to facilitating cloud migrations and improving integration with CI/CD tools, with future enhancements outlined in their public roadmap.

Shawn Sesna discusses a deployment issue encountered when using Octopus Deploy to manage SQL Server Integration Services (SSIS) packages developed in a newer version of Visual Studio, which included properties not recognized by an older SQL Server version. The error stemmed from a mismatch in connection manager properties, specifically "ConnectByProxy," that the older SQL Server could not process. While deploying directly from Visual Studio avoided the issue by not mapping package parameters to environment variables, using Octopus Deploy required a workaround. Sesna found two solutions: manually updating package parameters to use the default package setting, which was inefficient, or using a PowerShell script to automate the process, thus ensuring smoother deployments. The blog post aims to help others avoid similar challenges in SSIS package deployment, emphasizing the importance of compatibility between development tools and target servers.

Shawn Sesna's guide details the deployment of a Node.js application, specifically the BestBags e-commerce sample, using Octopus Deploy with a MongoDB back-end. The process begins with making the application more configurable by modifying port settings and database connection strings using Octostache syntax. The guide emphasizes using Liquibase to handle database deployments by creating a dbchangelog.xml file for MongoDB. It discusses using Bamboo as a build server to manage dependencies, package the application, and push build information to Octopus Deploy. The deployment process includes using Octopus Deploy to apply changes to MongoDB via Liquibase and setting up NGINX as a reverse proxy for the Node.js application. Each step is meticulously explained to ensure a seamless deployment, highlighting the integration of DevOps practices in managing and deploying Node.js applications effectively.

Matthew Casperson's comprehensive blog post, dated May 17, 2021, delves into the nuances of managing feature branches within the Octopus Deploy platform, particularly in the context of Azure environments. The article outlines the concept of a feature branch as a temporary source code branching pattern used for developing new features, which is not intended for production but for testing purposes. Casperson describes how feature branches can be effectively managed using Octopus through the creation of environments, lifecycles, and channels, with the help of tools such as Terraform and the Octopus CLI. He further explains the use of runbooks to automate the creation, deployment, and destruction of the necessary resources for feature branches, highlighting the processes of synchronizing with Git, saving costs by shutting down resources overnight, and ensuring that feature branch deployments remain short-lived and isolated from production. The blog emphasizes the importance of synchronizing Octopus with Git branches using scheduled triggers and scripts, ensuring that feature branches are accurately represented and managed within Octopus, thus enhancing the efficiency of development workflows in Azure PaaS environments.

PHP remains a dominant language for web-based applications, and the post illustrates how to deploy a PHP application using NGINX and MySQL, leveraging tools like Jenkins and Octopus Deploy for an efficient process. The highlighted sample application, the Car Rental Project, demonstrates the integration of a web front-end with a MySQL back-end, showcasing modifications made to the database connection configuration to support Azure MySQL PaaS's SSL requirements. The process involves packaging the application and database scripts using Jenkins, pushing them to Octopus Deploy, and executing a deployment process that includes creating a MySQL database, utilizing Flyway for database migrations, and deploying the PHP application to an NGINX web server. The configuration of NGINX involves setting necessary directives and bindings to run the PHP application, ultimately enabling a streamlined deployment process for PHP applications with database back-ends.

The article by Andrew Best explores the intricacies of designing a new software architecture, emphasizing the importance of a well-structured system that facilitates swift decision-making and adaptability to change. It describes the process of defining architecture, which involves setting clear goals aligned with business objectives, establishing constraints to limit complexity, and creating a common language for discussing emerging concepts. The piece highlights Octopus's efforts in developing a new architecture for deployment steps, focusing on simplicity, flexibility, and the ability to work with technologies beyond C#/.NET. It underscores the significance of collaborative decision-making, involving team input and expert scrutiny, to foresee system-level impacts and maintain a high-performing team. The text also addresses the challenges of both static and emergent complexities within architecture, advocating for detailed analysis and strategic constraints to manage these complexities effectively. Additionally, it stresses the importance of considering system quality attributes, or "ilities," such as maintainability, to ensure the architecture can evolve without disrupting existing systems. Overall, Best presents a comprehensive guide to crafting a robust software architecture that supports dynamic business needs and technological advancements.

Deploying Java-based applications to IBM WebSphere Liberty is facilitated by Octopus Deploy, which offers built-in steps for application deployment. IBM WebSphere Liberty, available in both paid and open-source versions, supports automatic application deployment by placing the application in a designated folder. The post details a step-by-step process to deploy the Java PetClinic application, leveraging a MySQL database backend, to WebSphere Liberty. This involves setting up the Liberty server, creating a server instance, and using Octopus Deploy features like custom deployment directories and structured configuration variables to manage database credentials and connection strings. The deployment process includes creating a database, managing user access, and migrating data with Flyway, while the application itself is deployed by placing it into the specific "dropins" folder on the server. The successful deployment can be verified by accessing the application through the default port 9080, demonstrating the streamlined approach to manage Java applications on WebSphere Liberty.

Shawn Sesna's article discusses the growing popularity of NoSQL databases like MongoDB, highlighting the automation of deployments using tools such as Octopus Deploy and Liquibase. The text explains the distinct differences between MongoDB and relational databases, notably in how collections and documents replace tables and rows, respectively. It details the use of Liquibase's changelog to create collections and insert documents in MongoDB, featuring examples of creating collections with specific validators and inserting diverse documents. Furthermore, the article describes a deployment process involving the creation of a MongoDB server, database, and user, including assigning roles and applying changesets via Liquibase, all facilitated by the Octopus Deploy platform. The deployment is verified using MongoDB Compass, ensuring the successful addition of databases, collections, and data. Additionally, the article promotes further learning through webinars on database DevOps using Liquibase and Octopus Deploy.

Deploying an Oracle database using Liquibase with Octopus Deploy can streamline the typically challenging process of database deployments by utilizing Liquibase's unique changelog feature, which allows migrations to be defined in formats like XML, JSON, and YAML, in addition to SQL. The post details the steps involved in incorporating a Liquibase step template within Octopus Deploy, emphasizing the importance of selecting the appropriate database type and providing necessary connection details like server name, port, and credentials. It also outlines additional steps like creating users, assigning roles, and generating change scripts for review before deployment. The example uses a sample project, Sakila, to demonstrate these procedures, showcasing how Octopus Deploy supports various database technologies and deployment methods, ultimately enhancing the efficiency and reliability of database updates.