We have multiple Rancher repositories with Windows CI in them and more than likely none of the CI follows the same pattern. We should create and publish a best practices for Windows CI along with drone/dapper templates that each Rancher team can integrate themselves.

The goal is for the Windows team to own the idea of creating the best practices but not be the ones to implement the CI itself.

This came up while discussing Fleet Windows CI issues with @nickgerace

Another idea: Build, publish, and maintain a Windows CI image that contains all required packages.