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

Use the Evergreen REST v2 API to download -latest tarballs in setup multiversion mongodb

    • Fully Compatible
    • v4.4
    • STM 2020-11-30, STM 2020-12-14
    • 15
    • 2

      There are caching policies for fastdl.mongodb.org and downloads.mongodb.com that cause --useLatest to download day-old or possibly month-old binaries even after the push task has succeeded on the older branches. Changing to use the /tasks/<task_id> endpoint (for example) would make it possible to download the files directly from S3.

        "name": "Binaries",
        "url": "https://s3.amazonaws.com/mciuploads/mongodb-mongo-v4.0/enterprise-rhel-62-64-bit/f35415816415b9ff93bb963690ac4f8c9f6bc453/binaries/mongo-mongodb_mongo_v4.0_enterprise_rhel_62_64_bit_f35415816415b9ff93bb963690ac4f8c9f6bc453_19_02_26_21_26_34.tgz",
        "visibility": "",
        "ignore_for_fetch": false

      An unfortunate consequence of using Evergreen to download binaries from older branches is that we would tie build variants across different mongodb-mongo-* Evergreen projects together when we haven't necessarily been consistent about naming. This means it won't always be possible to download the binaries from the build variant with the same name as the one that exists in mongodb-mongo-master and we may need to keep an explicit mapping in etc/evergreen.yml.

      We must also make a decision about whether we should depend on the push task succeeding, or only depend on compile, jsCore, dbtest, and replica_sets_jscore_passthrough succeeding as SERVER-35972 has changed for the 4.0 and master branches.

            mikhail.shchatko@mongodb.com Mikhail Shchatko
            max.hirschhorn@mongodb.com Max Hirschhorn
            0 Vote for this issue
            10 Start watching this issue