Skip to content
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

Some Valid Versioning usage in External Feeds (GitHub Nuget) will result in Package Not Found in Feed #6817

Closed
5 tasks done
millerjn21 opened this issue Apr 7, 2021 · 1 comment
Assignees
Labels
area/core feature/feeds kind/bug This issue represents a verified problem we are committed to solving

Comments

@millerjn21
Copy link

millerjn21 commented Apr 7, 2021

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

Using a GitHub Nuget external feed, some versioning will result in The package was not found in the feed. An example of this is #.#.#-AAA-####-AAAAA-AAAAA.###. This versioning is valid semver, but Octopus fails to pull in the details of the package on the release page. However, the package still deploys correctly. I would expect this behavior is not limited to GitHub Nuget feeds, but that is what I discovered and tested it on.

What I expected to happen

I would expect the release page to be able to find the package and get the information.

Steps to reproduce

  1. Create an external Nuget GH feed
  2. Push a package with versioning like the above example or below screenshot.
  3. Add the package to a step and create a release
  4. See the error

Screen capture

image

Affected versions

Octopus Server: Latest at time of writing (2021.1.6460)

Workarounds

Change the versioning schema of your package or ignore the error, as the package will still deploy correctly.

Links

Source Ticket: https://help.octopus.com/t/the-package-was-not-found-in-the-feed/26423/3
Internal Slack Convo: https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1616089126042000
Internal Cloud Repro: https://octopus-operations.octopus.app/app#/Spaces-83/projects/github-nuget-feed-tests/deployments/releases/0.0.1

Additional Ticket: https://octopus.zendesk.com/agent/tickets/71812

@millerjn21 millerjn21 added the kind/bug This issue represents a verified problem we are committed to solving label Apr 7, 2021
@N-lson
Copy link

N-lson commented Aug 9, 2021

This looks like it was fixed in #6949 - the earliest version this fix was added in was 2021.1.7599
Rerun of the internal cloud repro is now successful on build 7638: https://octopus-operations.octopus.app/app#/Spaces-83/projects/github-nuget-feed-tests/deployments/releases/0.0.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core feature/feeds kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants