4 ms·
We use Octopus Deploy at work to deploy .NET. There's a bit of a learning curve, and it has a few quirks and annoyances, and you might need to write some Powers
by cableshaft 10y ago
We use Octopus Deploy at work to deploy .NET. There's a bit of a learning curve, and it has a few quirks and annoyances, and you might need to write some Powershell scripts to fill in a few gaps (which it can run), but once you've got it in place, it's super simple to deploy everything. Every single deploy used to be a big hullabaloo at our company, now it's super smooth thanks to Octopus.
If you're talking about Ant, Maven, Tomcat, etc for Java deployment, it's been about 5 years since I've had to use that, but I'd say Octopus is a much better process than that.
- manyxcxi 10y agoWe tried using Octopus (3 years ago) as part of our CI/CD pipeline and ran into a big problem with it choking on file sizes and handling all the bundled dependencies we threw at it. Eventually we just scripted MSBuild and archived them ourselves for retrieval when we needed them.
- cableshaft 10y agoWe don't have anything too huge we give it. I think our largest package is like 100MB. But we do have about 40 active projects in its system. Also, I attended something by a guy who worked for Accenture, who talked about using it with thousands of active projects and some of the technical issues they had to overcome (and work directly with Octopus team to help resolve, at some points) with such a massive amount of projects. It was this guy that gave the talk, he has a blog with lots of information about his experience with Octopus. A few of the quirks I encountered when getting everything set up with our company were resolved by reading his blog: http://ianpaullin.com/category/octopus-deploy/ http://ianpaullin.com/category/octopus-deploy/