[SERVER-68109] setup_spawnhost_coredump script should notify user via Slack when it has finished running Created: 18/Jul/22 Updated: 29/Oct/23 Resolved: 19/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2022-07-25 | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
The wall command is great for having the banner to tell me when I've ssh'd in too early. Having the notification come through Slack when everything is finished means I would only need to look once though. Proposed Slack notification text: Linux
WindowsUsing Cygwin for remote debugging on Windows is strongly discouraged. We should steer Server engineers to use Windows Remote Desktop instead.
|
| Comments |
| Comment by Max Hirschhorn [ 19/Jul/22 ] | |||||||||
|
The changes from 0fa5c9a to handle how the setup_spawnhost_coredump script runs as the mci-exec user (and not the Administrator user) on Windows spawn hosts appear to be insufficient for getting Slack notifications to work. It is unclear what is different about how the hostSetupScriptJob in Evergreen runs the setup_spawnhost_coredump script compared to the steps which are simulated by hand.
| |||||||||
| Comment by Githook User [ 19/Jul/22 ] | |||||||||
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: | |||||||||
| Comment by Githook User [ 18/Jul/22 ] | |||||||||
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |