[CI] The windows CI doesn't include octomap

[SeanCurtis-TRI]

In the configuration for the windows CI under appveyor, octomap functionality is not included. The CI configuration is responsible for pulling libccd and eigen, but not octomap. We should strongly consider including it, or putting a clear warning that this doesn't happen and there is no guarantees as to the windows support being consistent.

Currently, the appveyor CI process is painfully slow. There isn't much parallelism and the hardware dedicated to the process renders each test painfully long. Adding octomap support will increase the cost of each test (decreasing the CI throughput). This might be the primary reason why we would decide to not include it in CI.

[traversaro]

Currently, the appveyor CI process is painfully slow. There isn't much parallelism and the hardware dedicated to the process renders each test painfully long. Adding octomap support will increase the cost of each test (decreasing the CI throughput). This might be the primary reason why we would decide to not include it in CI.

Switching to GitHub Actions-based Windows CI in my experienced solved many of these problems, so if you are interested I would be happy to open a PR adding CI on Windows with vcpkg-provided dependencies (including octomap) using GitHub Actions.

[SeanCurtis-TRI]

I"m game. I know nothing about it and would relish the chance to learn more. It would be a greatly appreciated contribution.

[jamiesnape]

I have a branch (among many) with new CI for Windows. They have just been waiting for the releases to happen.