you can put them in test. you probably want to add an alias to deps.edn that adds test to the classpath, and then have the test runner include that alias. a babashka task sounds like a good idea; it might just call something like (clojure "-M:test")

just took a look at what we have set up at work, and I think this should do the trick:

;; deps.edn
 :aliases {:extra-paths ["test"]
           :extra-deps {lambdaisland/kaocha {:mvn/version "1.0.629"}}}
# shell
clojure -M:test

I was thinking whether it would make sense to release this as part of the sample project of Biff. Because if I add my own configuration for myself then you may add this into the default and then I'd have to adjust it.

I probably will put something like this into the template project. The testing story has been on my todo list for a while, though it's still fairly far down there. I wouldn't worry about duplicating effort though. The example I pasted above is just two lines 🤷. plus updates to the template project are optional for existing projects; it's fine to just bump the biff version and leave the rest of your app alone. no need to stick to the defaults.

I didn't update the project's biff version, only the version of the tasks. Project uses "v0.7.11" and tasks use "v0.7.13". This happens in the start. Seems to be ok for now.

But after it compiles things it goes haywire (I entered my ssh password a couple of times):

I didn't really mind to enter my password twice and I was happy with "v0.7.9". That was not a problem and I didn't care. I simply wanted it to work reliably. That's it. I don't care if it does it twice (as long as it's not more than twice). It's not about ergonomics of entering/not entering my key.

hmmmm Looks like the ssh agent isn't working. It's not causing any problems; it's just not preventing you from being asked for your password five times. I just counted up the number of times that bb deploy will ask for your password if you don't have an ssh agent session working, and it is in fact five 🙂 . If you entered your password that last time in the second screenshot, that should be the last time it asks. I can re-refactor bb deploy so that the max number of times it asks for your password is two (an rsync call and an ssh call). I would like to get the ssh agent thing working still, but limiting the number of ssh/rsync calls would be good as a fallback. What output do you get if you run:

eval $(ssh-agent)
ssh-add
echo $?
ssh-add -l
ssh  echo hello

It failed on ssh-add:

If I do this it works but then I'll not have the issue and this won't be solved. It will be fixing my config but it won't solve the 5-times password thing. And yes. Currently ssh-add -l prints one key that I added.

If I try to deploy from a different terminal then it doesn't work. The first bb deploy call is with the version 9, the second call is with the version 13 (this white stripe is me removing title of the app):

> If I do this it works but then I'll not have the issue and this won't be solved. It will be fixing my config but it won't solve the 5-times password thing. I don't understand what you're saying here; can you rephrase? If you run ssh-add ~/.ssh/id_martin_digitalocean as in the first screenshot and then run bb deploy, does bb deploy still ask for your password? In any case I'm just trying to figure out where the root problem is so that if possible I can update biff to handle it. What output do you get from:

eval $(ssh-agent)
ssh-add
echo $?

> I'm wondering if for some reason ssh-add isn't inferring where your keyfile is I have 5 keys so I think that single ssh-add doesn't add the correct key. The digitalocean key is only used for this deployment and nothing else. I have separate keys for everything. What I did in the first screenshot was that I opened a second terminal and expected it all to work.

oh, yeah. I figured you probably had multiple ssh keys but didn't think through the implications, which I should have. ssh-add might be adding one of your other keys, or something. probably not much that's worth doing to try to handle that situation since I think even ssh sometimes has to just try each key one by one till it finds one that works. at least there's the message about keychain already. re: ssh-add and opening a new terminal: unless you're using keychain or you've set up ssh-agent in some other way so that it applies to your entire login session, the ssh-agent session is typically scoped to just the current terminal. so if you open a new one, you have to do eval $(ssh-agent); ssh-add <key file path> again. in any case, v0.7.14 should limit the password prompts to 2, so if that works then I think there's no other changes needed in the biff tasks for now. if the messages from bb deploy about keychain get annoying then you can set :biff.tasks/skip-ssh-agent true.

(I guess ssh/rsync does seem to be figuring out which key file it needs to decrypt, so there should be some way I can infer it the same way--but, eh. maybe I'll check if ssh-add can take a host name as a parameter or something)

It seems to work well. I think this is good. There's an error in the beginning and the instruction should also be good.

Perfect, thanks for testing that.