October 2016 Summaries

Octopus.Client is an open-source code library designed to facilitate the use of the Octopus REST API from .NET applications, including C#, PowerShell scripts, and LinqPad, enabling programmatic actions that mirror those possible through the web interface. Recently separated from the main codebase, it is now housed in the OctopusClients GitHub repository, where users can report issues or suggest improvements. The library adheres to Semantic Versioning, allowing for backward compatibility with Octopus Server while supporting the addition of new features. Additionally, Octopus.Client has been ported to .NET Core, supporting netstandard1.6 and .NET Framework 4.5, and offers an asynchronous API due to the .NET Standard's fully asynchronous HttpClient. The synchronous API remains available for the .NET Framework, ensuring backward compatibility, though a decision to deprecate it has not been made. Octo.exe, part of the same repository, has also been adapted for .NET Core, with a cross-platform version anticipated.

The text explores the complexities and benefits of multi-tenancy in deployment lifecycles, particularly in software projects like the Synergy project. It describes a typical lifecycle that progresses from Testing to Staging to Production and explains how different tenants, or customers, interact with these stages. Customer-1 and Customer-2 can deploy to both Staging and Production, while Customer-3 can only deploy directly to Production, illustrating the flexibility and challenges of tenant-aware deployments. The article discusses the concept of un-tenanted deployments, which can occur in any environment accessible to a tenant, and introduces an option to require tenants for all deployments to prevent unintentional un-tenanted deployments, especially to production environments. This feature supports more advanced configurations that some teams might adopt as they transition to fully tenanted architectures, allowing for more controlled and tailored deployment processes.