Octopus Deploy Documentation

Package Repositories

Last updated

When planning your Octopus installation, you need to decide how to host your packages. Your build server should create your packages and publish them to a package repository.

The Octopus Deploy server includes a built-in repository and supports the following external repositories:

Octopus can consume packages from multiple feeds at once if necessary.

Your package repository will typically be:

Choosing the Right Repository

Because Octopus can consume packages from multiple feeds, we recommend using different repositories for different purposes as each repository provides different benefits. For instance, if you produce your own application library packages in addition to your deployment packages you might consider something like the following:

  • Use the built-in repository for your deployment packages. This is generally the best choice as it offers better performance and through the retention policies you've configured, Octopus knows which packages are no longer required and can be cleaned up.
  • For application library packages consider using the repository provided by your build server, a file-share, MyGet, or Azure DevOps Package Management.
  • For deployment scripts that you want to store in your source control and where a build process is unnecessary, GitHub feeds might be suitable.

Planning Package Repository Placement

By default, when you deploy a package to a Tentacle, the package will be pushed from the Octopus server to the Tentacle. You can override this by changing the setting of the Action System Variable Octopus.Action.Package.DownloadOnTentacle from False to True. When set to True the package will be downloaded by the Tentacle, rather than pushed by the Octopus Server.

To reduce network latency, when your package repository is in close proximity to the Octopus server leave Octopus.Action.Package.DownloadOnTentacle set to the default value of False. Alternatively, if you have explicitly set the Tentacles to download packages by the Tentacle to True, you should consider placing your package repository in close proximity to your Tentacles.

In This Section

The following topics are explained further in this section:

Welcome! We use cookies and data about how you use our website allow us to improve the website and your experience, and resolve technical errors. Our website uses cookies and shares some of your data with third party analytics companies for these purposes. We do not use these cookies for advertising.

If you decline, we will respect your privacy. A single cookie will be used in your browser to remember your preference.