Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-89624

Clone Jepsen repo in 10gen/mongo-release using specific tags

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Correctness
    • v8.0, v7.3, v7.0, v6.0

      https://github.com/10gen/mongo-release/blob/master/evergreen/jepsen_docker/setup.sh currently clones a few Jepsen forks:

      git clone --branch=evergreen-master git@github.com:10gen/jepsen.git jepsen
...
git clone --branch=no-download-master git@github.com:10gen/jepsen-io-mongodb.git jepsen/docker/control/mongodb

      As well as https://github.com/10gen/mongo-release/blob/master/evergreen/do_jepsen_setup/install_jepsen.sh:

       git clone --branch=jepsen-mongodb-master --depth=1 git@github.com:10gen/jepsen.git jepsen-mongodb

      This makes it more volatile by cloning from a moving target. Release tags have been introduced in 
      jepsen-io-mongodb and 10gen/jepsen, and the cloning maneuver should anchor to those.
       

            Assignee:
            Unassigned Unassigned
            Reporter:
            steve.mcclure@mongodb.com Steve McClure
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: