Thanks! Very clever solution to provide such configuration) btw. there is a github action to provision different versions of graalvm as a part of your workflow - https://github.com/marketplace/actions/setup-graalvm-environment

Yes, I recommended this to @UJ1339K2B but he told me that this doesn't support setting up a development version.

@U04V4KLKC yep. Having dev version of Graal would be much appreciated

Does the action allows setting multiple Graal versions? If yes where the action set’s the base directory for each?

I think the point of this setup action is that it adds one version to the environment, we have a slightly different use case, or we should re-organize things in different jobs

I can add dev version today. each version installed in the separate directory following …/GraalVM/%graalvm-version%-%java-version%-%arch%/x64 notation. Also this action expose a set of environment variables: • JAVA_HOME • JAVA_HOME_%graalvm-version%.%java-version%.%arch% • GRAALVM_HOME first and last will be overwritten by the last action run but second will be present for every followup steps

ah right

so it is possible to provision multiple graalvm versions

so then you can just do setup-graalvm, execute test, setup-graalvm v2, execute test, etc.

setting GRAALVM_HOME is excellent because this is what most tools already use

Perhaps you can make it so that setup-graalvm adds always the latest dev version

This will also solve the problem for us that our builds will fail when the dev version is removed

yes, I’m already working on it while we are speaking )

cool! 🙏

Or we can override GRAALVM_HOME from our test suite :D

@UJ1339K2B I think we can just make a github matrix and use setup-graalvm

Ah right.

Cool idea.

Thank you @U04V4KLKC :man-bowing:🙏🙏

https://github.com/DeLaGuardo/setup-graalvm/pull/20/checks?check_run_id=3700067176 I manage to add suport for latest nightly build. But it requires slight adjustments in workflow file. 1. graalvm: “nightly” 2. personal-token: ${{ secrets.GITHUB_TOKEN }}

right now it exposes the same set of env variables except JAVA_HOME_%version%. Because version is unknown before run I expose “JAVA_HOME_NIGHTLY”

That's not a problem

Thanks!

released as 5.0 version

Nice! I have a use for this at work immediately to replace the ad hoc stuff we're currently doing. And thank you for using clj-new and build-clj!

Thanks, Sean. Great to hear. And yeah, clj-new definitely made it super easy to publish to Clojars, which was nice.