SSH private key authentication and Jenkins Blue Ocean #88
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antonio-petricca
changed the title
daniel-beck
reviewed
Apr 4, 2018
| // advantage of the auto generated SSH key... | ||
|
|
||
| sshagent (credentials: ['jenkins-generated-ssh-key']) { | ||
| sh 'git config core.sshCommand "ssh -v -o StrictHostKeyChecking=no"' |
There was a problem hiding this comment.
Is StrictHostKeyChecking=no really something we want to recommend as a best practice?
There was a problem hiding this comment.
It is the only way to make it working. I got it from the SSH Agent plugin official guide.
Thank you so much
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added a sample code to push to git by the Jenkins Blue Ocean auto generated SSH key.
I have added some tweaking to avoid SSH key verification errors, too.