Clicking the "Spawn..." link for an Evergreen and leaving the "Load data for ... onto host at startup" checkbox checked would cause Evergreen to run the evergreen fetch command after the host is provisioned. The evergreen fetch command would download any artifacts attached to the task using the s3.put or attach.artifacts commands as well as any artifacts attached to the tasks it depends on (e.g the compile task). Now that uploading the debug symbols has been moved to a separate upload_debug_symbols task and no tasks depend on the upload_debug_symbols task, the tarball containing the debug symbols are not downloaded by the evergreen fetch command.

We should run the attach.artifacts command as part of the compile task to preserve the old behavior.

[
  {
    "name": "mongo-debugsymbols.tgz",
    "link": "https://s3.amazonaws.com/mciuploads/${mongo_debugsymbols}",
    "visibility": "public"
  }
]

Separately, we should remove the ignore_artifacts_for_spawn that's being specified to the attach.artifacts command in the etc/evergreen.yml project configuration file because it isn't actually used by Evergreen. Whether the artifacts are downloaded on a spawn host is controlled by an ignore_for_fetch parameter within the file description itself.