ci: Include tracking of GOOS for which Caddy fails to build

[mohammed90]

We learned about the build failure for Solaris by accident. Perhaps it's better we have track of which OSs Caddy fails to build for to have an understanding our areas of improvements and where we are probably unable to support.

Updates #3615

[francislavoie]

I'll dig deeper later but at a glance:

[francislavoie]

FYI @mholt unfortunately github actions doesn't have a "warning" state for jobs yet, but there's an open issue discussing it here actions/runner#2347

So for now, we have continue-on-error: true set for this stuff so that it doesn't make the PR go red for any cross-build failures, but the only other option is green. To see the failures you can look at the annotations on the workflow: https://github.com/caddyserver/caddy/actions/runs/187524216

[mholt]

This looks cool, neat idea!

I can see why this would be even better with some sort of "warning" result instead of just green/red.

I guess something we can add to our TODO list is to submit patches upstream, or at least request that they make their build tags more correct, so that we can continue to build x-platform.

[mholt]

Is this ready to merge or should we wait? Is it even useful if it always emits a green status?

[mohammed90]

Is this ready to merge or should we wait? Is it even useful if it always emits a green status?

It is ready. The results always being green bothers me too, but I hope the workflow being listed reminds to check for annotations... until Github Actions supports tri-state results.

[mohammed90]

Blocked by #3625 😓 (kinda, sorta)

[mholt]

My bad. Will get that figured out soon.

[mholt]

Okie all fixed