We are using Octopus for our deployment to different environments. But we found that it always packages the complete solution and deploys it to the next level. Is it possible to put some restrictions - like do not copy and deploy the config folders. In our case we just need to deploy some specific folders and not the complete packaged solution. Is this possible with Octopus.


Yes.. we can control the packages using nuspec file which will be added to your solution and you will be specifying the list of folders/files you dont wanna deploy. And you will use that nuspec to create the nuget package for deployments


As far as I know, I think Octopus doesn't packages anything. The package should come from your CI Tool (Jenkins or TeamCity maybe?)

Having said that, I would check on your previous step in the CI/CD chain to see how are you packaging your solution, and filter those folders there, before packaging.

That will also help you:

  • Reducing the package size
  • Increase speed in the deployment process
  • Avoid storing unnecessary files

High-level suggested CI/CD Chain summary

CI Tool

1. Compile/Test (if you're working with a compiled language)
2. Package only required folders
3. Push to Octopus

Octopus (CD Tool)

1. Store and manage final packages

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.