Context

Coverity scan of any code base that uses typed language(s) require the code to be built. Currently, the build command being used for Coverity scan of mongo-go-driver is make build, __ which is of course is failing because of the move to taskfile.

Definition of done

DevProd would recommend that Coverity scans for Go driver be run as an Evergreen task. DevProd has created an Evergreen function which can be included in any Evergreen task and it will run the scans and push results to Coverity web server. Here is the documentation on this: https://docs.devprod.prod.corp.mongodb.com/coverity/runningCoverityInEvergreen

Pitfalls

What should the implementer watch out for? What are the risks?