SERVER-114165 Disable Coverity scanning on release branches (#44204)

GitOrigin-RevId: a6ef473a2450115ef943fb83fb839f9d8a7f4c49

.github/CODEOWNERS

@@ -356,6 +356,9 @@ WORKSPACE.bazel @10gen/devprod-build @svc-auto-approve-bot
 /docs/**/poetry_execution.md @10gen/devprod-correctness @svc-auto-approve-bot
 /docs/**/server_parameters.md @10gen/server-programmability @svc-auto-approve-bot
 
+# The following patterns are parsed from ./docs/branching/OWNERS.yml
+/docs/branching/**/* @10gen/server-release @svc-auto-approve-bot
+
 # The following patterns are parsed from ./docs/evergreen-testing/OWNERS.yml
 /docs/evergreen-testing/ @10gen/devprod-correctness @svc-auto-approve-bot
 

docs/branching/OWNERS.yml

@@ -0,0 +1,5 @@
+version: 1.0.0
+filters:
+  - "*":
+    approvers:
+      - 10gen/server-release

docs/branching/README.md

@@ -176,6 +176,11 @@ bazel run lint format
 
 Run linters and formatters and fix anything that couldn't be autofixed.
 
+#### Disable Coverity scans on release branch
+
+Since Coverity scans will automatically run on the new \*-staging branch, we can disable Coverity scanning on the release branch itself.
+Create `ENABLE_COVERITY_ANALYSIS` variable in the Evegreen project settings for the release branch and set the value `false`
+
 ## 3. Test changes
 
 In case working branch was created from `master` branch, rebase it on a new `vX.Y` branch and fix file conflicts if any.

etc/evergreen_yml_components/variants/coverity.yml

@@ -3,6 +3,7 @@ buildvariants:
     display_name: Coverity Analysis
     # Don't run Coverity analysis as part of patch builds
     patchable: false
+    activate: {ENABLE_COVERITY_ANALYSIS!|true}
     allow_for_git_tag: false
     # Run at 4 am UTC everyday
     cron: "30 4 * * *"