[SERVER-31553] Update multiversion tests on 3.6 and master branches Created: 13/Oct/17  Updated: 30/Oct/23  Resolved: 28/Nov/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.7.1

Type: Task Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-31558 Bump verify_versions_test.js from 3.5... Closed
related to SERVER-31985 Modify and re-enable multiversion tes... Closed
related to SERVER-32460 Determine and remove featureCompatibi... Closed
related to SERVER-32461 Determine and remove featureCompatibi... Closed
related to SERVER-32463 Determine and remove featureCompatibi... Closed
related to SERVER-32466 Determine and remove featureCompatibi... Closed
related to SERVER-35152 Update multiversion tests on 4.0 and ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-11-13, Storage 2017-12-04
Participants:
Linked BF Score: 0

 Description   

Similar to SERVER-27107, after branching 3.6, we should bump the version in the following places:
For master branch:

  1. update multiversion to download 3.6: https://github.com/mongodb/mongo/blob/r3.6.0-rc0/etc/evergreen.yml#L975
  2. update https://github.com/mongodb/mongo/blob/r3.6.0-rc0/src/mongo/shell/servers.js#L126
  3. bump verify_versions_test.js from 3.6 to 3.7
  4. remove any multiversion tests that are specifically testing 3.4 <~~> 3.6 upgrade/downgrade scenarios.


 Comments   
Comment by Githook User [ 27/Dec/17 ]

Author:

{'email': 'maria@mongodb.com', 'username': 'mvankeulen94', 'name': 'Maria van Keulen'}

Message: SERVER-31553 Remove outdated upgrade/downgrade test
Branch: master
https://github.com/mongodb/mongo/commit/6a6d6b898089a170e411cf8a899f99208e7ab7e8

Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}

Message: SERVER-31553 Update multiversion tests on 3.6
Branch: master
https://github.com/mongodb/mongo/commit/2975b0dc56c66150585788896652915ab40a405f

Comment by Max Hirschhorn [ 15/Nov/17 ]

I was wondering what kind of changes the 3.6 branch needs here.
For all the configuration-like files, I don't think they need changes.
For all the multiversion tests, I don't see they require changes either, though i'm not sure if 3.6 branch will continue to translate "latest" as "3.6".

xiangyu.yao, it shouldn't be necessary to make any changes to the contents of the jstests/multiVersion/ directory on the 3.6 branch. Specifying binVersion="latest" should look for a mongod binary without any version suffix in its filename.

bump verify_versions_test.js from 3.6 to 3.7

I pushed a change for this so the Evergreen build would go back to being green for the multiversion* tasks.

Comment by Githook User [ 15/Nov/17 ]

Author:

{'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-31553 Bump current version in verify_versions_test.js to 3.7.
Branch: master
https://github.com/mongodb/mongo/commit/8e3fecc8bbfc081e626bf98188a16fb22237c8d7

Comment by Xiangyu Yao (Inactive) [ 15/Nov/17 ]

max.hirschhorn I was wondering what kind of changes the 3.6 branch needs here.
For all the configuration-like files, I don't think they need changes.
For all the multiversion tests, I don't see they require changes either, though i'm not sure if 3.6 branch will continue to translate "latest" as "3.6".

Comment by Max Hirschhorn [ 13/Oct/17 ]

We should also remove any multiversion tests that are specifically testing 3.4 <~~> 3.6 upgrade/downgrade scenarios.

Generated at Thu Feb 08 04:27:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.