Closed yurishkuro closed 2 years ago
Also, it's still puzzles me why the CLI doesn't exit with an error code when it fails. We can control whether the check itself is required or not via repo setting, but in the current state it just fails silently and looks like everything is green.
I fixed the GOPATH issue in #552, but the FOSSA action still fails https://github.com/jaegertracing/jaeger-client-go/pull/553/checks?check_run_id=1465159886
It does not seem to understand pre-go-modules local vendor
, even with GO111MODULE=off (#553).
Sample build:
Most likely this is due to this repo not using go modules, so in order to build it we need some special setup as in https://github.com/jaegertracing/jaeger-client-go/blob/1b586b71ff1a76b4390b6b0c6f3f9552e33d927b/.github/workflows/unit-tests.yml#L24
@idvoretskyi can you confirm that FOSSA needs to run in the repository where normal go build commands work? Without go modules, it means being in the right path under GOPATH and having initialized
vendor/
dir.