Replies: 4 comments
-
Sounds good! I also have GitHub Actions, however the download speed has not yet been an issue for me. However it takes 2m 23s in one of my projects so this sounds like a good idea! |
Beta Was this translation helpful? Give feedback.
-
Realized that I don't have the permission to make the published image public right now, so I've reverted above change. |
Beta Was this translation helpful? Give feedback.
-
Yeah noticed, I was surprised you got to it so quickly. I'll continue with other things meanwhile, entropy and all that ... looking forward to having it on ghcr eventually 🙏 |
Beta Was this translation helpful? Give feedback.
-
We have now the permission to publish to https://github.com/orgs/NordicPlayground/packages?repo_name=nrf-docker, so I'll look into this soon™️. |
Beta Was this translation helpful? Give feedback.
-
Hi!
We have a few Zephyr/nRF related repositories, one of them is a private repo. for the end customer firmware. When we tag a release there we'd like to have everything needed to rebuild/patch/fix from that tag a few years down the line, relying on our GitHub action to rebuild with the same build deps used when we created the tag.
This nrf-docker project looks exactly like what I wanted to set up myself. Have you considered pushing the resulting Docker images also to the GitHub Container Repository, ghcr.io? This would greatly speed up download and build times for GitHub actions.
If you're interested, here's an example of what I did to automate our pandoc docker image to push to ghcr.io:
Cheers
/Joachim
Beta Was this translation helpful? Give feedback.
All reactions