I would like to push back the results from a build to github and I therefore use the Git publisher plugin. However, when I try to add the SSH public key from Cloudbees as a Deploy Key on Github then Github tells me: 'Key already in use' since it is also part of another repository.
I would like to know why I cannot use the same public key for multiple independent repositories?
[update] The answers so far indicate that the question is unclear. Cloudbees generates a key pair and uses this on github, I've not found a way to create an alternate pair, so I am stuck with one pair.
I've added the public key to repo A so Cloudbees can pull from repo A. However, I want to use the same build to push to repo B. So it seems logical to add the same (my personal Cloudbees key) to to repo B so cloudbees can push to repo B as well.
However, on Github only a single repo can be using the deploy key:
A deploy key is an SSH key that is stored on the server and grants access to a single repo on GitHub. This key is attached directly to the repo instead of to a user account.
So it is clear that the the public key cannot be attached to more than one repo. However, I can't think of a reason why this is the case?
Anybody?