Closed marcusmueller closed 3 years ago
Hm, this looks interesting, although for builds on docker cloud this is uncessary as the whole stack will be rebuild without caching anything anyhow. So compared to the previous version this would always pull the latest volk release?
The trick here is that the ADD command used on the latest release JSON from Github to invalidate the cache iff that has changed. (RUN itself would not be executed again.)
Only touched the currently master-activated workers.
It might be worth somehow automagically triggering a worker rebuild upon a release being released on gnuradio/volk.