|
ryan.egesdahl@mongodb.com I don't know how it was working before either, I probably just picked the v6.0-latest suffix because it somehow looked "more precise" to me. But we are intending to look at nightly builds, so if you say using -latest is correct, then that's what we'll do! (cc augi.liebster@mongodb.com let me know if you want me to reopen any linked issues)
|
|
geoff.mishkin@mongodb.com I did a bit more of an in-depth look at this, and I think I understand what's going on now. The reason you were not able to find a tarball with a -v6.0-latest suffix is because the Evergreen version you were looking at was not a release build. If you want to always test against a release build, you will need to look specifically for the Evergreen version at the tagged commit. On the other hand, if your intention was to look at nightly builds against the branch, the -latest suffix is correct. Either way, I don't think this is functioning incorrectly, but I still don't quite understand how this was working for you before the version_expansions_gen task was added. Could you provide a little more detail on what you're trying to do and how it was working before?
|