Reflecting on the benefits of continuous integration tools, I'm wondering whether our focus on great CI support has meant Octopus is too hard to simply get started with. How can we improve the getting started story?
I'll be hosting a webinar to demonstrate the new features in Octopus 1.5: Azure deployments, FTP/FTPS, ScriptCS and more
Packaging formats and artifact repositories are essential to continuous delivery. Here are my dreams for a universal packaging format.
Looking for comments on two features we're currently building: Azure and FTP support
A guest blog post by Jonathan Goldman on his open source project that makes it easier to share PowerShell scripts in Octopus projects.
Steven Kuhn works on Octopus Deploy part time
A code project article written recently about Halibut, which is a lightweight secure alternative to WCF, written for .NET/Mono
Octopus 1.4 includes the ability to update release variables, clone projects and disabling machines.