1. The difference between the two
SSH keys are for the account dimension, can have read-only access, you can read, write permissions, you can read, write, delete, permissions assigned permissions to others
deploy keys is for the project dimensions, and only read-only access
ssh keys have a corresponding account some privileges
2. How to mistake their own ssh keys configured to deloy keys to solve
ssh key generation see above blog post (git ssh key generation step https://www.cnblogs.com/ringbell/p/6262193.html)
Click on the project, deploy keys to configure ssh key to the project. At this point you modify the code corresponding to the local authority will be prompted to push the issue again
The reason for this problem:
deploy keys permissions are read-only permission for the deployment, use Jenkins release, you can see each project has the deploy keys for jenkins
Solution four steps:
[1] The configuration deploy keys fail. Click on items found deploy keys, click the corresponding button to the right of the disable deploy keys on the failure (changes to enable)
[2] corresponds account was mistakenly see ssh keys to find the secret key configuration deploy keys with the ssh keys, found after clicking the delete icon on the right to delete
[3] will delete the local configuration ssh keys
[4] regenerate ssh keys (git ssh key generation step https://www.cnblogs.com/ringbell/p/6262193.html)