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 GitHub2) 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
