Source downloads not found after 6.0.12 and 7.0.4

Graham_Parker1 · 2024-07-22T11:06:17.508Z

Hi,

I noticed the source downloads beyond versions 6.0.12 & 7.0.4 (both released Nov 27th 2023) don’t exist, and just wondered if the file naming had changed, perhaps if that stage of the build pipeline might be failing since then or maybe they aren’t being published anymore?

For example, this works:

https://fastdl.mongodb.org/src/mongodb-src-r6.0.12.tar.gz

But not:

https://fastdl.mongodb.org/src/mongodb-src-r6.0.13.tar.gz

Thanks very much for any thoughts or help with this

chris · 2024-07-22T14:20:59.604Z

Not sure about the whys or wherefores, but they are available directly from GitHub:

curl -OJL https://github.com/mongodb/mongo/archive/refs/tags/r7.0.5.tar.gz

Graham_Parker · 2024-07-25T12:02:50.221Z

Thanks very much Chris! Is there anywhere you would recommend I raise the question to see if it was intentional or not to stop publishing the files on the fastdl server?

Cheers!

chris · 2024-07-25T22:21:34.304Z

@Graham_Parker You could also try a JIRA issue.

https://jira.mongodb.org

Graham_Parker1 · 2024-08-06T06:05:16.846Z

Thanks again Chris, after reading that I created [SERVER-92955] Missing source tarballs on fastdl, github workaround missing version.json - MongoDB Jira.

In case it helps others coming across this question, MongoDB’s reply was that “to simplify our release process during a recent refactor these artifacts are no longer no being produced”.

Further details were provided, which are helpful too:

"As you identify, version.json is not included in the tarball. Typically the version.json is generated locally when someone is building a version that they want to name in a particular way.

As a workaround, I see two options:

Clone the repo and checkout the relevant release that you’d like to build locally:

git clone GitHub - mongodb/mongo: The MongoDB Database cd mongo git checkout r6.0.12

Have your build script create a version.json file before it starts.

Given these two workarounds, and the complexity of addressing this issue within the described workflow I’m going to resolve this ticket. But, please let me know if you have questions about either workaround."