Silly question perhaps. We’re attempting to implement a new continuous integration environment using TeamCity+OctopusDepoy. I can build out server product fine, but am struggling with how to correctly define a NuGet package and configure Octopus Deploy to install the newly build executables in that NuGet package.
For our server product, we build a bunch C++ x64 executables with a single Visual Studio solution. Right now each of those executables is packed into the same NuGet package — on words A.exe, B.exe, C.exe, D.exe, E.exe and F.exe.
For deployment, each logical server is comprised of multiple physical boxes running Windows Server. Typically we have 3 types pf physical boxes (ex. Uno, Dos and Tres) when Uno needs A.exe. B.exe and F.exe each installed as a Windows Services, where Dos needs C.exe, D.exe and F.exe and Tres gets E.exe and F.exe. But some times we might instead have an Uno that gets all (i.e, A.exe, B.exe, … , F.exe) and no Dos or Tres whatsoever.
My questions is, what is the best approach for setting up the NuGet package and configure Octopus Deploy to auto-manage such an environment?
Any advice folks can offer would be greatly appreciated.
Thanks.