April 2018 Summaries

Octopus Deploy Containers enable users to run Octopus Server or Tentacle directly within a Docker container, simplifying the setup and upgrade process by ensuring the availability of the latest versions through the octopusdeploy/octopusdeploy and octopusdeploy/tentacle images. The process involves using Docker commands to run the server, configure mount points for persistent storage, and map web portal ports, while allowing for custom admin credentials. Tentacle containers, although less frequently used for certain tasks, offer potential for future enhancements in deployment operations. Additionally, Docker Compose can be leveraged to create a self-contained environment with a SQL Server and Octopus Server, suitable for testing and experimentation. This containerization capability reflects Octopus Deploy's commitment to integrating with container technology, with plans for further enhancements like Kubernetes integration to improve deployment processes across platforms.

Octopus Deploy facilitates seamless integration with leading cloud services such as Amazon Web Services (AWS) and Microsoft's Azure platform, simplifying the deployment of applications securely. While integrating with AWS involves straightforward steps of adding an Access Key and Secret Key, Azure integration is slightly more complex, requiring four specific values for authentication and secure interaction: Azure Subscription ID, Azure AD Tenant ID, Azure AD Registered Application ID, and Azure AD Registered Application Password/Key. These values, mostly GUIDs, can be retrieved from the Azure Portal or via Powershell, and a video tutorial is available to guide users through the setup process. The article encourages users to consult the Azure documentation for detailed instructions on creating Octopus Azure accounts and addresses security and permission concerns, while also inviting feedback and promoting their YouTube channel for more instructional content.

Octopus Deploy, a release-management and deployment-automation tool, is enhancing its support for Platform-as-a-Service (PaaS) endpoints like Azure Web Apps and Service Fabric by modeling them as deployment targets, which allows for improved visibility, role assignment, and integration with operations processes. This shift addresses past limitations, particularly around the dynamic provisioning of infrastructure, by enabling deployment steps to communicate with the Octopus server to add new targets during deployment processes. The 2018.5 release introduces licensing changes, where PaaS targets will begin contributing to licensing limits, aligning with the increasing trend of PaaS adoption. The update aims to facilitate easier management of environments and sets the stage for future features related to dynamic provisioning and operational process execution, with no breaking changes to existing configurations.

In a "Will it Deploy?" episode, Rob Pearson demonstrates how to automate the deployment of an ASP.NET MVC 5 web application to Microsoft Azure App Service using AppVeyor and Octopus Deploy. The app in focus is a simple random quote generator, offering a practical example of setting up a cloud-based delivery pipeline. The process involves committing the source code to GitHub, automatically building the app with AppVeyor, and deploying it to Azure using Octopus. The deployment setup is straightforward, utilizing an Octopus Deploy Azure Web App step and enabling configuration changes through variable replacement during deployment, allowing updates to the web.config file. This episode's GitHub repository provides all the resources used, and viewers are encouraged to suggest new technologies for exploration in future episodes while subscribing to the YouTube channel for regular updates.

The April 2018 release of Octopus Deploy introduced several significant updates, including the highly anticipated Recurring Scheduled Deployments, which allows users to trigger deployments on a regular basis, enhancing automation for tasks such as daily testing or scheduled infrastructure management. Additionally, the release improved integration with Amazon Web Services by introducing a first-class S3 step, streamlining the process of managing packages and files in the AWS ecosystem. The update also introduced the capability to mark certain deployment steps as required, preventing them from being skipped, and addressed user requests for more control over deployment processes. A notable change involved the Automatic Release Creation (ARC) feature, which now enforces channel constraints to manage pre-release package selection, marking a shift from previous behavior. Users are encouraged to review the release notes for guidance on upgrading and to provide feedback on the new features.

AppVeyor, a cloud-hosted continuous integration tool popular among open-source projects, has integrated support for Octopus Deploy, simplifying the process of setting up a scalable continuous deployment pipeline without managing infrastructure. By using AppVeyor's new Octopus plugin, developers can automate the deployment of projects, such as a simple ASP.NET MVC app, to both staging and production environments easily. The integration allows for the creation of a delivery pipeline that packages applications and pushes them to Octopus Deploy, automating the release process. This collaboration enables version-controlled configuration through an appveyor.yml file, facilitating seamless updates and deployments tied directly to the source code. The Octopus Deploy step further allows for environment-specific configurations, ensuring that variable replacements and web.config transformations are applied during deployment, thus maintaining consistency between testing and production environments. The combined use of AppVeyor and Octopus Deploy provides a reliable, automated solution for continuous delivery, eliminating the need for custom scripting and manual interventions.