Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59809

Use project_identifier instead of project_id in setup multiversion

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Fully Compatible
    • STM 2021-09-20
    • 0

      Evergreen API provides project_identifier field to reference the "real" project name in 5.0: https://evergreen.mongodb.com/rest/v2/tasks/mongodb_mongo_v5.0_enterprise_rhel_80_64_bit_archive_dist_test_2b0d538db8c0c9b9d7992d4489ba7171c721dfb7_21_09_02_18_49_46

      project_id worked fine for 4.4 and master projects because it also contained "real" project name before:
      https://evergreen.mongodb.com/rest/v2/tasks/mongodb_mongo_v4.4_enterprise_rhel_80_64_bit_compile_83b8bb8b6b325d8d8d3dfd2ad9f744bdad7d6ca0_21_07_28_19_54_00
      https://evergreen.mongodb.com/rest/v2/tasks/mongodb_mongo_master_enterprise_rhel_80_64_bit_archive_dist_test_911e585044f76bb244f425066bfcb838e9dfb258_21_06_02_01_18_12

      And now we need to update this in setup multiversion since we want to introduce 5.0 branch for jstestfuzz self tests (TIG-3280)

            Assignee:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Reporter:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: