Thank-you for the dev effort that goes into making Julia what it is.
Spinning up ephemeral containers/VM’s for running test suites. Linux primarily.
That developer effort means Julia is evolving rapidly.
Which means distro/packaged builds aren’t always available.
Even were they do become available, there is value to allowing power-users to tweak their builds.
This raises an issue in test/spec/behavior driven dev environments.
Wherein you’d like to be confident your test env reflects “your” julia build. The issue is the build time prohibits building Julia each time you spin up your test stack.
Also there is more than one version of julia ‘live’.
Furthermore some projects are fine running on ‘old’ versions, but package updates need to be tested. etc. etc.
There can easily be a lot of julia builds in play in-the-wild.
I doubt I’m the first to encounter this issue.
What seems to be ideal is a built ‘julia’ volume that is shared between containers/VM’s.
Has anyone beaten this path already?
How are people handling this?