[SERVER-21039] Use consistent names for tagging baseline builds Created: 20/Oct/15 Updated: 23/Oct/15 Resolved: 22/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chung-yen Chang | Assignee: | Chung-yen Chang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Performance B (11/02/15) |
| Participants: |
| Description |
|
We have two naming schemes for tagging the baseline builds used for performance comparison in Evergreen. For mongo-perf tests, we follow the format of 3.0.x-Baseline. For system performance and longevity projects, we use 3.0.x-BASELINE. This inconsistency is annoying and the sooner we fix it the better, so we avoid any possible complications in the future. |
| Comments |
| Comment by Githook User [ 22/Oct/15 ] |
|
Author: {u'username': u'chungyen100', u'name': u'Chung-Yen Chang', u'email': u'chung-yen.chang@10gen.com'}Message: |