Deploy Squirrel applications with Octopus

Hey all,

I’m interested if someone has managed to deploy a Squirrel installer (https://github.com/Squirrel/Squirrel.Windows) with the Octopus workflow. I’ve had a ClickOnce deployment running just fine with it, but with Squirrel I need access to the nupkg, the ability to run some XML transform, and finally run a command line to push it to a UNC location. So it actually never reaches a remote machine to be installed.
I realise Octopus has a different primary focus for delivery, but I wanted to know if someone has manged to figure out a way to do this.

Thanks for any input on this,
C.

Hi Christos,

Thanks for getting in touch! We don’t use Squirrel ourselves but there is a community member that wrote a blog post that might help you solve your problem (https://chaseflorell.github.io/devops/2015/08/07/deploying-squirrel.windows-apps-with-octopus-deploy).

Please let me know if this doesn’t solve your problem.

Pawel

I’ve described the flow I’m using here: http://help.octopusdeploy.com/discussions/questions/4925-client-applicationsquirrel

Will have to lok at the blogpost above to see if it’s a better approach. Still a lot of moving parts…

Hi Peter,

Thanks for getting in touch! The only other suggestion I can make is to package your app twice so you end up with a nuget file containing another nuget file with your application. In this way when Octopus extracts the top level nuget package you end up with a nuget package instead of a folder with bunch of files. I know, it is another workaround but at the moment Octopus doesn’t do out of the box what you are looking for.

Please let me know if this doesn’t solve your problem.

Regards

Pawel