New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External Feed test in Octopus 3.4.0 fails to find the same packages as earlier versions of Octopus #2656
Comments
|
So after a day of testing this against TeamCity, NuGet.org and MyGet.org it is only the TeamCity NuGet feed that is returning inconsistent results between Octopus I also modified the package search logic to find packages by package id, but this endpoint is case-sensitive so searching for So I'm not quite sure where we should go from here. |
Another user reported this on the same ticket: http://help.octopusdeploy.com/discussions/problems/39739-octopus-teamcity-and-an-empty-feed#comment_40689607 |
After further investigation, it turns out this is related to the upgrade to NuGet v3 libraries. If you use Octopus 3.3.27 (which uses older NuGet libs) everything works fine. The newer NuGet libraries perform searches on a different endpoint and are now case sensitive. For example, using Fiddler to proxy the requests being made under the hood, if we setup a TeamCity external feed, we can see that the older Octopus 3.3.27 (with older v2 NuGet packages) queries the following URLs:
Whereas the latest Octopus (with the v3 NuGet packages) ends up querying a different endpoint altogether (and I could not find a way to make the new NuGet library query the other Packages endpoint):
I'll discuss this with the team, but as we're relying on third-party libraries (NuGet), we are limited on the functionality available to us. |
Looks like this issue is now blocking a deployment: http://help.octopusdeploy.com/discussions/questions/9909 |
We've also had customers coming along with related issues with TeamCity 7-8 like this: Source: http://help.octopusdeploy.com/discussions/problems/47581-teamcity-nuget-feed |
Hi all It seems as if we are experiencing the same issue with our Artifactory Pro (version 4.16.0) since we updated to Octopus 3.4.15. Nuget packages of "stable" versions (like e.g. 1.6.23) are not found anymore, although they are definitely available in Artifactory (and have already been deployed to different environments with the previous version of Octopus...). Was there any progress made on this issue? Thanks |
We have had no further reports, so it looks like the the various feed fixes around the |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately. |
This is currently blocked until we can ship #2926
Testing an external NuGet feed (TeamCity 10) in
3.4.0
seems to yield different results to Octopus2.x
(for example).Searching for
octopack
in 2.x:Searching for
OctoPack
in 3.x (testing for case-sensitivity)Manual search using browser: http://build.octopushq.com/guestAuth/app/nuget/v1/FeedService.svc/FindPackagesById()?id=%27OctoPack%27
The text was updated successfully, but these errors were encountered: