Ci teamcity6/19/2023 ![]() ![]() Once added, the TeamCity feed will appear in the NuGet feed list. In the Octopus Web Portal navigate to Library ➜ External Feeds.nupkg will automatically be served as NuGet packages, which Octopus can consume. You can enable this by navigating to Administration ➜ Nuget Settings and enabling the inbuilt NuGet server. TeamCity 7 and above can act as a NuGet repository. Consuming the TeamCity NuGet feed in Octopus Simply click the Show examples link to see options to upload packages including the repository URL. You'll find the URL to your repository on the Library ➜ Packages tab in Octopus. OctoPack will then push the packages when the solution is built. To push packages to Octopus during the OctoPack phase, enter the NuGet endpoint URL into the Publish packages to http field, and an API key in the Publish API Key field. Octopus can be used as a NuGet package repository, or it can be configured to use an external feed (such as retrieving them from TeamCity). OctoPack will ensure these packages appear in the artifacts tab of TeamCity: With these options selected, your packages will automatically be created using the version number of the current build. Make sure this evaluates to a multi-part number, for instance, 1.1.3., or 1.0.%unter% to include the build ![]() The package version cannot be a single number (learn about version numbers in Octopus).
0 Comments
Leave a Reply. |