From 9d3a785183b9ed4f7d10365d31b9aa02e1e4743e Mon Sep 17 00:00:00 2001 From: Trevor Guidry Date: Wed, 26 Nov 2025 13:02:07 -0600 Subject: [PATCH] Revert "SERVER-114165 Disable Coverity scanning on release branches (#44204)" (#44467) GitOrigin-RevId: d6518cd549718708cb0e151191766eec869e5681 --- docs/branching/README.md | 5 ----- etc/evergreen_yml_components/variants/coverity.yml | 1 - 2 files changed, 6 deletions(-) diff --git a/docs/branching/README.md b/docs/branching/README.md index e257e285f46..b9c8cc20b2c 100644 --- a/docs/branching/README.md +++ b/docs/branching/README.md @@ -176,11 +176,6 @@ 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. diff --git a/etc/evergreen_yml_components/variants/coverity.yml b/etc/evergreen_yml_components/variants/coverity.yml index d2b03a0be35..1b78e45c106 100644 --- a/etc/evergreen_yml_components/variants/coverity.yml +++ b/etc/evergreen_yml_components/variants/coverity.yml @@ -3,7 +3,6 @@ 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 * * *"