Support Transferring GitHub Caches & Artifacts over Azure ExpressRoute #119721
Replies: 1 comment
-
Thanks for sharing this feedback @ajschmidt8! You can check our public roadmap to see the kinds of work we are focusing on for the coming year. Smaller fixes won’t be listed, but are often included when work is happening adjacent to it. While it has been a while since we have updated on this thread, the absence of an update is simply that - there has been no update because there is so far nothing to report. That doesn't mean it isn't being worked on - it might simply be that we're unable to share details about work that isn't ready for release. As a GitHub user, the most you can do is to share your feedback on this Discussion space with the correct tags (include examples), and trust that we are always working to make GitHub as awesome as possible. We can't guarantee that every bit of feedback sees action, but we are paying attention. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Azure ExpressRoute enables customers to directly connect their data center to Azure.
Presumably, GitHub Actions caches and artifacts are stored somewhere in Azure.
However, it doesn't seem that GitHub Actions supports transferring workflow caches and artifacts to self-hosted runners over ExpressRoute.
Transferring GitHub Actions caches and artifacts over ExpressRoute would help ensure that transfers to and from self-hosted runners are fast and reliable.
It would also help bandwidth-conscious teams move cache and artifact transfer bandwidth away from their internet links.
Therefore, I would like to request this feature.
Beta Was this translation helpful? Give feedback.
All reactions