Tag: Octopus Deploy Pro Tip
-
Setting up continuous deployments with Octopus Deploy and TFS
One reader asked in my Octo.exe deep dive if I had published how to setup continuous deployments. I had mentioned it in the deep dive and while I’d rather do a comprehensive piece to see how many different ways we could set up a continuous deployment, a simple post on how to setup continuous deployments in TFS is…
-
From the frontline: Upgrading the Octopus Deploy Server
Note: I’ve had this post ready for months but completely forgot about it. It’s about four months out of date, but still interesting so I’ve decided to post it anyway. We’ve been planning on upgrading for months (since late 2014), but with a jam packed schedule it was difficult to fit in. On top of…
-
Octo.exe – exporting/importing project pitfalls
Over a year ago, I mentioned that the Octo.exe supports the ability to export a project from one server to another server. This feature last year needed a lot of work and was a bit difficult to understand, but at the time I didn’t have a pressing need for it. After working with it extensively over…
-
From the frontline: Octopus Server performance tuning
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. We decided on Octopus in February and our pilot testing started in late March early April with a handful of teams and users. Our shiny server (*ahem* virtual machine) with Octopus Deploy was chugging along and we all…
-
Backing up projects on Octopus Tentacles? Think twice
I’ve noticed many of our Octopus teams use the File System – Backup Directory step template from the library to implement a backup step. Unfortunately, I’ve seen minimal prudence from said teams implementing backups. Many of these teams simply backup their project across most if not all of their environments while having no rollback steps whatsoever. Don’t get me wrong,…
-
OctoPack error: Could not find a part of the path
If you’re managing numerous Octopus projects across an enterprise, you’re bound to run into an error you’ve never seen before. Most frequently for us, that comes with the build process. Users often confuse (by no fault of their own) the source of the error being the OctoPack but in my experience, the OctoPack in and of itself…
-
OctoPack error: Cannot add part for the specified URI because it is already in the package
Recently, I had an issue with a project team’s TFS build and the OctoPack. Within the TFS log, I found this error: OctoPack error OCTONUGET: Cannot add part for the specified URI because it is already in the package. After some google-fu, I found a helpful post on StackOverflow. Short answer: you have to remove any duplicate references…