Support Transferring GitHub Caches & Artifacts over Azure ExpressRoute #132735
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
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 the ability to transfer GitHub workflow caches and artifacts over Azure ExpressRoute.
Beta Was this translation helpful? Give feedback.
All reactions