consider switching to new fork of jsch?

[tommy-mor]

Current jsch does not support the new openssh key format.
I was getting this exception

WARN  lambdacd-git.ssh - Problems adding custom identity file.
com.jcraft.jsch.JSchException: invalid privatekey:

This led me to this thread, which suggests updating jsch to this version which is more maintained.

Or you can convert your ssh keys to the old version as suggested in the SO thread.

Maybe just leave a note or point to this issue in the docs somewhere?

[tommy-mor]

the default ssh-keygen on my machine generates a key with the -----BEGIN OPENSSH PRIVATE KEY----- header, which is not supported by current version of jgit (according to "invalid privatekey" exception and SO thread).

generating a key using ssh-keygen -m PEM as suggested by the stackoverflow thread fails because github does not support RSA-1 keys anymore.

I had to use ssh-agent (probably better anyway). but Its a bit troubling that as far as I can tell, using the :identity-file key directly is no longer compatible with github.

[flosell]

Hi @tommy-mor - thanks for reporting this! LambdaCD as far as I can tell isn't widely used anymore so I've stopped actively maintaining it a while ago.
So unfortunately, it's unlikely me or someone else in the (small) community will spend time on this in the near future. However, I'm happy to review, merge and release PRs.

[tommy-mor]

that makes sense. Do you know what people do use these days for clojure CD/CI?

[flosell]

I'm assuming same as the rest of the software world, many moving to hosted products, GitHub Actions, GitLab CI, Circle CI, the various cloud provider offerings, ...
All of them support pipelines as "code" (YAML...) now, they are a lot less hassle to operate and I guess few need the power and flexibility that'd come from something like LambdaCD.