Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-12912

Virtual envs are confusing in Evergreen

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Evergreen
    • Storage Engines
    • StorEng - Defined Pipeline

      In our Evergreen file, we create virtual env every at different places. The way we have things written now, we may create multiple virtual env because of the following pattern:

        - name: many-collection-test
          commands:
            - func: "compile mongodb" -> Creates a virtual env
            - command: shell.exec
              params:
                working_dir: mongo-tests/largescale
                shell: bash
                script: |
                  set -o errexit
                  set -o verbose
                  ${PREPARE_PATH}
                  virtualenv -p python3 venv -> Creates another virtual env
                  source venv/bin/activate
      

      It would be better to have a function to create a virtual env and every subsequent step would benefit from it.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: