Diagnosing deployment failures for keyboards

Every now and then it is possible for a deployment to fail. This notes a few steps you can take for diagnosing keyboard deployment failures.

1. Check the keyboard name and version on master branch on https://github.com/keymanapp/keyboards/.
2. Check the keyboards build on https://build.palaso.org and ensure that the keyboard built successfully (check logs).
3. Check https://downloads.keyman.com/keyboards/ for the version uploaded.
4. Check https://github.com/keymanapp/s.keyman.com/tree/master/keyboard/ for the version uploaded for KeymanWeb.
5. Check https://help.keyman.com/keyboard/_name_ for the version uploaded.
6. Check https://api.keyman.com/keyboard/_name_ for the version on api.keyman.com
7. Check https://api.keyman.com/ to see latest database build date
8. Check api.keyman.com azure control -- web job for database build to review build logs
9. Download https://downloads.keyman.com/data/keyboard_info.zip to look at .keyboard_info and verify its contents
10. Check cloudflare caching (there may be pages to purge?)
11. On api.keyman.com azure control, check D:\home\site\wwwroot\.data\keyboard_info\_name_.keyboard_info and verify its contents