Deploy keys broken between 4.2 and 5.1
Created by: asgrim
I have upgraded from 4.2 (to 5.0) to 5.1. One of our users triggered a build in Jenkins, which failed to pull the refs. I go to view the deploy keys for the project, and I see this message:
"They can be used for for CI, staging or production servers. A deploy key can be added to only one project. If you need to add the same key to multiple projects you can create a deploy user and add that user to multiple projects."
This functionality is now broken, just because you have written a message to say "do this workaround", this still really needs to be fixed. Having to create a user that contains just deploy keys is a really awful workaround.
If I cannot add the same key to multiple projects, that is a crazy limitation!