Historically Octopus Deploy was a solution to deploy software on Windows only, therefore the server component only supports installation on Windows.
This is for a couple of technical reasons:
Octopus Server takes a hard dependency on Internet Information Services (IIS) which itself only runs on Windows.
Octopus Server is written in the .NET Framework doesn'...
Helm is a Kubernetes tool so this answer assumes you are deploying to Kubernetes or OpenShift not Docker Swarm.
If you are using Helm well then I don't think it is particularly important what build pipeline tech you are using to invoke it. I think what is more important is how you manage all your configuration within Git and how you structure the Helm ...
It appears that Octopus supports a push from BitBucket, but not a pull (https://octopus.com/blog/bitbucket-pipes-and-octopus-deploy)
Github supports either option: https://octopus.com/docs/packaging-applications/package-repositories/github-feeds
Octopus can be configured as either the target of a push from GitHub or you can set up a feed in Github, and pull from that feed.
In your case, it sounds like you want a push mechanism, such as GitHub Actions to do the heavy lifting.
So you need to create packages for each of the three sites so that you can deploy each one individually.
The first step is to create a .nuspec file for each of the IIS websites you want to package:
Install OctoPack and read the entire article
Create three empty text files next to the .csproj, give it the same base filename as the .csproj, thus if it is ...
It can be achieved, however, you will make your life easier if you modify your TeamCity build process to create a package for each IIS Website then deploy each one individually using a Deploy to IIS step.
If it's impossible to change your build process then you will need to do some pre-processing or just deploy the websites through a custom script.
Octopus can now be launched in a docker container in linux -
Octopus Server Linux Containers launched as part of 2020.6 and it's our recommended way to use containers with Octopus Deploy. You will need to upgrade to 2020.6 before using the Octopus Linux Container....
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
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