PackageCompiler.jl
PackageCompiler.jl copied to clipboard
JuliaLang
Testing apps should ideally upload the app somewhere and then download it on another machine which doesn't have Julia
Similar as to how the julia buildbot works to check that we do not have assumptions about the current machine built into the app.
This seems like a really important test to have.
@KristofferC Do you have any ideas how we might implement this test?
Could run the app test inside a container with no Julia install. (Would still be the same machine, but at least paths etc that are built into the app will fail.)
Could run the app test inside a container with no Julia install. (Would still be the same machine, but at least paths etc that are built into the app will fail.)
This seems like a good first step!
Maye this could be performed with github actions. We created an automated github actions build script for our project, which compiles on the github servers and attaches the zipped binaries to the tagged release.
It is also possible to upload artifacts with github actions, which seem to be in some temparary storage.
The steps for testing could be something like:
- Compile on github and upload artifacts. Trigger a second workflow
- Download artifacts on a new instance without julia and run tests
One tricky part is that the GitHub-hosted GHA runners all have Julia installed by default.