[SERVER-45586] The enterprise module is not linted in patch builds Created: 15/Jan/20 Updated: 29/Oct/23 Resolved: 28/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | Mathew Robinson (Inactive) |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Run a lint task in a patch build with changes to the enterprise module that should cause the lint task to fail. |
| Sprint: | Dev Platform 2020-02-10, Dev Platform 2020-02-24, Dev Platform 2020-03-09 |
| Participants: |
| Description |
|
In lint runs during patch build (including the commit queue), we only look at what files have been changed in order to not need to run lint against the entire code base. However, this diff does not include any of the changes from the enterprise module. This means that changes to the enterprise module can break lint and wouldn't get caught until lint is running in the mainline. We should update lint runs that are part of a patch build to include any related enterprise changes as well. |
| Comments |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'name': 'Mathew Robinson', 'username': 'chasinglogic', 'email': 'mathew@chasinglogic.io'}Message: |