Ok, figured it out, but it looks like you already added the CB pubkey to your account as a deploy key, so we can't re-use it 'til it's gone from there, I think. I'm also not sure if we can re-use a deploy key on multiple repos in general, so we may need to create a new account that has that key and push rights only to the mirror repos we create.
A. On Sun, May 12, 2013 at 8:22 AM, Andrew Bayer <[email protected]>wrote: > So I can't figure out how to add a key to CloudBees other than public > keys, so I'm gonna leave this to you, ap. =) > > A. > > > On Sat, May 11, 2013 at 8:04 PM, Andrew Phillips <[email protected]>wrote: > >> Actually, that sounds perfect - I didn't know there was a way to store >>> the key for use across ephemeral slaves. >>> >> >> Coolio! In that case, how about the following: >> >> 1) Create a test repo jclouds/jclouds-mirror-test on GitHub >> 2) Create a deploy key for that job and modify the CloudBees job to >> mirror to there >> 3) Test with a sample PR to see how it's affected by the mirroring >> (unless we know already that it won't cause any problems) >> >> ? >> >> ap >> > >
