search

jenkinsci / google-compute-engine-plugin

https://plugins.jenkins.io/google-compute-engine/
Apache License 2.0
57 stars 88 forks source link

Support user specified ssh key #175

Closed jsoref closed 1 month ago

jsoref commented 4 years ago

101 seems to try to set the ssh key via metadata.

Unfortunately, that isn't working for our system where another file system gets mounted over the jenkins user's home directory (which already has an ssh key that the jenkins master has been using to connect to our image-templated instances).

We'd like to be able to specify the ssh key that jenkins uses to connect to the vm.

This doesn't seem to contradict #138.

I was able to start a google-compute-engine-plugin instance node, ssh from the jenkins master (using the key we already baked into our image/overlay), copy the ssh google-compute-engine-plugin generated public key from the metadata and append it to the ~jenkins/.ssh/authorized_keys file and w/ that, the plugin was able to connect.

I'm willing to do the work for this if you don't want to write it but are open to the code.

pbrownrobo commented 1 month ago

errr... seems like this was fixed in current version?

jsoref commented 1 month ago

Shrug. We're no longer running jenkins