featurebase/.gitlab
Seebs da4fb4ab4e stop uploading test results to sonarcloud, stop telling it we did
This gets complicated. For coverage output, sonarcloud supports wildcards.
For test output, it doesn't. So we weren't getting meaningful results,
just weird error messages. I fixed that, and got thousands of lines of
other error messages because it wasn't finding the test source files.
That looked like this:

	WARN: Failed to find test file for package
	github.com/molecula/featurebase/v3 and test
	TestTranslation_Primary

But we don't actually need the test reports sent to SonarCloud, because
"which parts of your test suite are being run" is sort of inherently
"basically all of them" with go test. So rather than continuing to do
that, we drop it.

Since we're dropping that, we don't need the JSON output from go test
anymore, so we drop that too, and the tee commands, and the "artifacts"
from the tee commands, and now our test output is human-readable and
slightly faster.

We also bump SonarCloud to 4.7.

We also fix the tests to use GOVERSION sometimes and GOFUTURE other
times, and bump from 1.19.2 to 1.19.3.

Also a couple of minor cleanup (adding explanatory comments,
combining adjacent grep commands, etc.)
2022-11-16 15:31:06 -06:00
..
.gitlab-ci.yml stop uploading test results to sonarcloud, stop telling it we did 2022-11-16 15:31:06 -06:00
.perf-able-gitlab-ci.yml drop PLG builds and related functionality, streamline phases 2022-10-14 09:49:19 -05:00
batch-ci.yml stop uploading test results to sonarcloud, stop telling it we did 2022-11-16 15:31:06 -06:00
Dockerfile fix broken dockerfile 2022-01-27 10:55:20 -06:00