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

Only publish the docs from the WiredTiger develop Evergreen project

    • Type: Icon: Build Failure Build Failure
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 5.0.4, 5.2.0, 5.1.0-rc1, 4.4.11
    • Affects Version/s: None
    • Component/s: None
    • Labels:

      doc-update failed on ~ Documentation update

      Host: ec2-34-239-1-64.compute-1.amazonaws.com
      Project: WiredTiger (mongodb-5.0)
      Commit: diff: Merge branch 'mongodb-master' into mongodb-5.0 | 23 Sep 21 06:45 UTC
      Evergreen Subscription: ; Evergreen Event:

      Task Logs (doc-update)

      Description of the issue:

      This issue is present on any branch that has an evergreen project and does not correspond to our develop branch.

      The task doc-update is described here.

      In the function update wiredtiger docs, we exit if we are not on the develop branch:

                if [[ "${branch_name}" != "develop" ]]; then
                  echo "We only run the documentation update task on the WiredTiger (develop) Evergreen project."
                  exit 0

      We thought it would exit the whole function but in fact, it does not. It jumps to the next command. Since the next command starts from the directory wiredtiger.github.com and it does not exist, we end up having the failure shown in Evergreen:

      Command failed: directory /data/mci/d1ff7486f4ef0588fa8921f35ba4e178/wiredtiger.github.com does not exist 

      Suggested solutions:

      After discussing with the Evergreen team, there are two suggested solutions:

      • Add the check against the develop branch in here. We will need to change the working_dir as¬†wiredtiger.github.com might not exist.
      • Or create a noop.txt file and check for its existence. If it exists, exit the function. We still need to change the working_dir.

            luke.chen@mongodb.com Luke Chen
            xgen-evg-user Xgen-Evergreen-User
            0 Vote for this issue
            2 Start watching this issue