Replies: 2 comments 1 reply
-
Hi there @johnc-ftl and welcome to our community! Thank you for the feedback! |
Beta Was this translation helpful? Give feedback.
1 reply
-
Same for me. We are considering git/issue-tracker/wiki cloud platform to migrate from our self-hosted environment. And have number of free-style projects built with make and deploying artifacts to nexus raw repo locally (e.g. MSI installers). There are "generic packages" in gitlab so I was pretty surprised there is no straightforward way to do it with github. Any workaround? Converting those projects to maven build is not an option... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It seems like an oversight that there is no "generic" packages support in github packages. I should be able to publish and fetch a zip (or other archive) file that is not a container, maven package, npm packages, or nuget package. Maven, npm, and nuget packages are useful for sharing libraries, but none of these are appropriate for an application installer, or other types of application packages or build output. Not everyone uses containers for all installations.
I note that there is an issue for generic packages on the roadmap, but it's been pushed out a few times, and I have no ability to comment on it. I'm pretty surprised that this wasn't included in the initial package support.
The API seems to require a specific package type (eg container). We'd like to migrate to github actions for our builds and deploys, but this is effectively a blocker for us. We're currently using Azure DevOps Artifacts Universal Packages for this purpose.
Related to #36023
Beta Was this translation helpful? Give feedback.
All reactions