Remove logic in etc/evergreen.yml to create a branch that tracks the remote branch

XMLWordPrintableJSON

    • Fully Compatible
    • v3.4
    • TIG 2017-02-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The workaround in SERVER-27126 used git branch --force to attempt to future-proof the Server team's etc/evergreen.yml project configuration from the effects of EVG-1327. However, it isn't possible to update the reference for the branch currently checked out. Since EVG-1327 has been complete, this logic in the etc/evergreen.yml projection configuration can be deleted from the master and 3.4 branches.

      [2017/01/27 17:06:56.567] # Create a branch in the git repository that tracks the remote branch configured for this
[2017/01/27 17:06:56.567] # Evergreen project so that the `git merge-base <branchname>@{upstream} HEAD` command run
[2017/01/27 17:06:56.567] # by the burn_in_tests.py script works.
[2017/01/27 17:06:56.567] git branch --force master origin/master
[2017/01/27 17:06:56.569] fatal: Cannot force update the current branch.
[2017/01/27 17:06:56.570] Command failed: exit status 128

            Assignee:
            Max Hirschhorn
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: