Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Are there any plans to implement authentication for GitHub Packages via GitHub App for access from, e.g., Jenkins?
I'm new to GitHub Packages and came with some expectations. I tried to go through the available documentation and blogs, and somehow was misled into thinking that I could use a GIT_TOKEN generated by a GitHub App to authenticate a Jenkins build, so it can download the corresponding Maven jars.
Only after many trials did I come across this clear section in the documentation: https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages, learning that it is only possible to use a PAT for that purpose.
In the context of CI, the use of a PAT is inconvenient, as it requires the setting up of a new account just for this purpose. I was hoping that this had already been considered and included in a milestone for sometime in the near future. Otherwise, I'll need to reconsider switching from Nexus to GitHub Packages.
Beta Was this translation helpful? Give feedback.
All reactions