You don't need direct shell access to run commands. If you are in a "simple" environment where there aren't a bunch of jenkins slaves, you can just create a new jenkins job with a "build script" to create the SSH key. http://stackoverflow.com/questions/10767488/automate-ssh-keygen-t-rsa-so-it-does-not-ask-for-a-passphrase

ssh-keygen -t rsa -f ~/.ssh/id_rsa -N ''

echo "SSH Public Key:
cat ~/.ssh/id_rsa.pub


Then take the output from the job and put it into a "new account" in github, grant that account read only access to your repo (since it doesn't have a password). Then some guy named Robert will be your parents sibling (Bob's your uncle).

It would be nice if it was just fixed tho, of course

~tommy

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to