Octo.exe export/import caveat: octo.exe versions matter
After doing numerous migrations using the octo.exe version 2.6.1.52, I decided to upgrade and move to version 2.6.3.59. As always, […]
After doing numerous migrations using the octo.exe version 2.6.1.52, I decided to upgrade and move to version 2.6.3.59. As always, […]
One reader asked in my Octo.exe deep dive if I had published how to setup continuous deployments. I had mentioned it in
Note: I’ve had this post ready for months but completely forgot about it. It’s about four months out of date,
Over a year ago, I mentioned that the Octo.exe supports the ability to export a project from one server to another
We’ve been running Octopus Deploy since 2.0 back in January 2014 as part of our head-to-head battle royale with Release Management 2013.
If you’re managing numerous Octopus projects across an enterprise, you’re bound to run into an error you’ve never seen before. Most
Rarely, if ever, does the OctoPack or for that matter NuGet.exe, miss a file or files that teams are looking
Recently, I had an issue with a project team’s TFS build and the OctoPack. Within the TFS log, I found this error:
I was asked at the CNUG meetup last month on Octopus Deploy on how to target Windows XP machines. At first,
I’ve run into this situation several times at work and thought I’d post it so I’d have no excuse as