Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-3679

Staging should push artifacts to a different path than production

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: app
    • Labels:

      Description

      We should use an expansion in the self-tests.yml to push staging artifacts to a different place than production because

      1. Production and staging artifacts may differ if, for example, hosts change in one environment but not the other.
      2. Pushing to the same place led us to misunderstand the symptoms of a problem with s3.puts as not connected to an agent deploy, because we missed that staging, which already had the bug, had already caused the problem, even though production did not yet have a bug.
      3. Although unlikely, it's possible that testing done in staging could have delete or modify artifacts that we depend on from production.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-evg Backlog - Evergreen Team
            Reporter:
            brian.samek Brian Samek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: