Having a CI profile setting :local-repo is one idea

I guess update-in as well but not sure how to combine it with a getenv

You can eval in from env vars in the project.clj.

This is similar to something I had setup for a similar case before.

You should also be able to update-in though if you wanted to go that route. Something like:

lein update-in : assoc :local-repo "$CUSTOM_LOCAL_REPO" -- <task>

There is support for this in the :mvn/local-repo key in the deps edn

And you can pass these dynamically on the command line with -Sdeps

clj -Sdeps ‘{:mvn/local-repo “whatever”}’

Or the do the right quotey thing with an env var there

This is for the Clojure CLI but maybe I misunderstood and you are using lein ?

Oh, we are in leinigen, my bad I probably just confused it all :)

@U0LK1552A you can also use lein change assoc :local-repo "path/to/somewhere" if you want to persist the changes to the project.clj file in case multiple commands are invoked separately during CI

@U064X3EF3 minor caveat: tools.build will not see that information unless you patch the code that creates a basis. I learned this the hard way when invoking clojure exactly as you described for a project that uses tools.deps

the solution in the end was patching the build.clj file since tools.build does not pick up certain keys from Sdeps IME

@U0479UCF48H that doesn't seem accurate, but feel free to follow up in #C6QH853H8 or #C02B5GHQWP4 if you have more on that

ahh ~( is what it is, and java.lang potentially being required is the other thing I hadn't realized. tyvm guys