Only a single private repository per organisation is supported

[dougjohnson]

trafficstars

Private repository support was added recently (see #6), which is fantastic - thank you so much! The implementation as far as I can see depends on a single global deploy key being set with an expectation that this can be reused across all private repositories.

Unfortunately, as can be seen in the GitHub documentation here, deploy keys must be unique across an organisation.

As a consequence, adding a new DotCI job for a second private repository in the same organisation results in this error:

Is it a mis-configuration by me that is causing this, or is it a genuine issue?

[suryagaddipati]

@dougjohnson Yes it is a genuine issue. I misunderstood how deploy keys work when I implemented this feature. Current implementation is wrong. Thank you bringing this up.

[samriley]

For the time being you can get round this issue by creating a jenkins user on github and ensuring that it has appropriate permissions, then when adding a private repo immediately delete the deploy key.

[zimbatm]

Would it be possible to make a release that doesn't try to create the key if the field is empty ?

[suryagaddipati]

@zimbatm Its on my roadmap. May be try the the workaround mentioned by @samriley in the meantime.

[ronwsmith]

+1 to get this fixed.

@samriley, to clarify, why do you need to delete the deploy key, and are you deleting it from github or Jenkins?

[samriley]

You delete them from github.

If you have a user set up that can access the repo then you dont need the deploy key. It's then just a case of deleting the deploy key on github so that dotci can add the key to another repo.

I think I spotted a fix committed recently-ish, so this might not be needed on the latest version.