When you create a change through a PR in Tentacle, a whole lot of processes spring into action. This document tries to outline all the steps that happen.
As mentioned in the Readme, when you create a PR, a TeamCity build process kicks off.
Teamcity pushes all the artifacts generated by the build process into Artifactory. These artifacts include installers for the various platforms Tentacle can be installed on.
Artifactory holds the nuget packages for every build of Tentacle. You'll notice that for every build, Tentacle has two nupkg versions - one for the self-contained Tentacle which can run without the .NET Framework and one for the .NET Framework version.
After the Teamcity build pushes to our non-public storage systems for Tentacle, the Octopus Deploy process then takes over and starts to deploy to public-facing locations.
During the deployment, Octopus calls the Slipway API to create a Tentacle release in Slipway.
This in turn allows the Tentacle to become visible on Slipway
and on the Downloads page.
Octopus also calls Chocolatey (self-contained version/.NET Framework version) to make Tentacle available as a Chocolatey Community package.
When a user runs choco install octopusdeploy.tentacle.selfcontained, it actually runs the chocolateyInstall.ps1 script. During the packaging process, the urls are replaced by the correct version numbers.