You can take a look at ssh-keyscan help build known_hosts databases (maybe you are using that). The man page even says it can collect 1000s of host keys in tens of seconds.
Our Jenkins instance happens to be managed by Puppet which can do ssh host key propagation for you, but it seems overkill if you aren't already using it. On Wed, May 20, 2015 at 5:03 PM, VFloyd <[email protected]> wrote: > Afternoon - > How do you guys handle the "Host Key Verification Failed" msgs when > deploying to new servers. > > I have 9 new build/deploy servers - one job can run on any of those deploy > servers to move code to 12 servers in an environment. > > ssh'ing from each of the 9 new servers to each of the 12 servers for one job > is not a problem and has already been done. But ssh'ing from each of the 9 > servers to 1000's of other servers could become a problem (more so if > someone decides to rebuild a random server or two). > > Any advise is appreciated. > > Vanetta > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/bed0b7b2-4d7e-48e7-b47c-cd29ecded3df%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAHNqWNPxC4tyJEZZopVwB0MudUs_%3DLPqkVs4FhnDenOGSrBycw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
