We have a separate GitHub repository where our configuration files live. We only have one release and one tag 0.0.1
Testing shows the GitHub Feed recognizes our repository, however it is not displaying a 0.0.1 version.
We have an enterprise github account, this repository is internal to our organization, I am the owner of the repository, and I am using my PAT for the purpose of this proof of concept.
What am I doing wrong?
Thanks for reaching out.
What kind of package feed are you hosting in GitHub? I’ve only ever setup and worked with a Nuget feed in GitHub, but I’m more than happy to tinker around with what you’re using and ask around internally. Can you please send me a screenshot of your feed settings in Octopus? If you need to you can DM me screenshots that have information that you’d rather not be public, or you can also send it to email@example.com. If you email us please include a link to this thread.
Looking forward to hearing back.
Appreciate your response. This may be the issue, as I did not realize we had to configure a package feed for GitHub. I was under the impression based on this article that using an Octopus GitHub Feed would use GitHub releases for the packages.
Incidentally, I created a package versioned 1.0.0 after reading the Semantic versioning 2.0 documentation. Strictly speaking, 1.0.0 is the first publicly available version, so I thought maybe that is why Octopus was not returning the version. Still same issue, no version is shown as in the screen shots above.
I’ve just run a quick test on this and found that the version doesn’t seem to get returned when using the Test Package option on the feed.
However, if you create a release for a project using a package on this feed it should grab the version correctly.
We’re unsure why the version isn’t returned on the test package screen and will check with our engineering team to see if this is a bug or limitation.
Thanks for the response. Two things:
First, I want to use the GitHub Feed for a script package only. The package actually being deployed is from a different repository. Based on your documentation here, I was expecting that using a GitHub Feed I set up in Octopus as the source for a Script Package and it would automatically download the latest SemVer 2.0 version of that package for my use during the deployment process.
Second, the Script Package is using the version that we use for the package we are actually deploying. Based upon the above documentation, I would expect it to be selecting the latest version (1.0.0) from the GitHub Feed.
Are separate repositories not supported by Octopus GitHub Feed?
Appreciate your help,
Thanks for all of the information.
Octopus grabs the latest version based on semver, and 2021.21.102 is technically newer than 1.0.0, so the behavior you’re seeing is to be expected. It’s based solely on the version and not the upload date.
If I’m misunderstanding the scenario, please let me know. If you need do DM me screenshots with sensitive information to explain further that could be helpful, or you can also email firstname.lastname@example.org and just mention this thread.
Looking forward to hearing back.
I also got clarification from our devs that it’s a known limitation that the test feed functionality won’t show versions as it was a performance choice. The way GitHub feeds work it takes extra API calls to return the versions so it’s reserved for the actual usage and ignored on the Test. I’m going to add this to our documentation.
@paul.calvert @jeremy.miller I have everything working now. Appreciate your help.
You’re very welcome! Thanks for letting me know you’re in a good state.
If you run into any other snags we’re here to help. I hope you have a great weekend.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.