Automating Deployments with Octopus Deploy Presentation
Forgive me for my misuse of Internet memes to make points with the crowd. 🙂
@ianpaullin
-
As an only child, I don’t have a clue what having a sibling is like. Having watched both of my kids, I think I’m sl… twitter.com/i/web/status/1… -
We have had a long time @AzureDevOps ask to automatically change the state of a parent work item depending on state… twitter.com/i/web/status/1… -
@TechTrainerTim Handmaid's Tale & Mindhunter. Never heard of Peaky Blinders.
-
I want to thank the @ChicagoBears for this opening season game as it’s reminded me why I switched to the @Seahawks… twitter.com/i/web/status/1…
-
@KSamChi @sesamestreet @mwpastore Have you met the nightmare for parents known as “Baby Shark”? https://t.co/7Zor2759Te
Hi Ian,
what would be the restrictions of Octopus? It seems that you projects are very oriented to .NET environment.
Today, there are few restrictions for Octopus. Octopus is first and foremost a .NET based deployment automation tool – however, tentacles today (version 3.x) are supporting SSH endpoints with a handful of Linux based OSes with mono support (Ubuntu and RHEL). You can read more about it here: http://docs.octopusdeploy.com/display/OD/SSH+Targets
Got it. Thanks a lot for the answer Ian.
VSTS comes with it’s release management.
In that case does *”RM – high pricing! Octopus – simple and very affordable” still hold good.
This presentation is over 4 years old. Pricing has changed for both VSTS RM as well as Octopus and – to add to the mix of products, Octopus Cloud service is coming some time this year. So pricing-wise, I would not rely on this slide deck being accurate for either Octopus and VSTS.