ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • 9.1.0-rc0, 9.1.0-rc1026
    • Affects Version/s: None
    • Component/s: None
    • None
    • R&D Security
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Overview

      Run the monguard-baseline-scan Evergreen build variant only on mongodb-mongo-master, not on the release staging branches.

      Background

      The variant runs an Endor Labs baseline scan of the monguard Rust crate. It is defined in etc/evergreen_yml_components/variants/misc/misc.yml, which the staging branches also pick up, so the Rust scan runs on branches where it is not wanted.

      Scope of Work

      * etc/evergreen_yml_components/variants/misc/misc.yml — remove the monguard-baseline-scan variant
      * etc/evergreen_yml_components/variants/misc/misc_master_branch_only.yml — add the variant, with its settings unchanged (commit-only requester, same paths filter on monguard/Cargo.toml and monguard/Cargo.lock, same task)

      Acceptance Criteria

      * The variant is defined only in the master-only variants file, which is included from etc/evergreen.yml
      * Evergreen configuration validates
      * Behavior on mongodb-mongo-master is unchanged

      Technical Notes

      * The release staging branches (v7.0-staging through v9.0-staging) have their own copies of misc.yml, so they are not affected by a master change
      * endorctl-pr-scan stays in misc.yml; it runs only on explicit patches

            Assignee:
            Jason Hills
            Reporter:
            Jason Hills
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: