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

Jenkins jobs don't clean up properly before build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-04-17, Storage 2017-05-08

      Description

      There was a recent build failure in the pull request tester, that made me notice that the pre-job cleanup in many of our Jenkins jobs isn't doing the right thing at the moment.

      The failure was:
      http://build.wiredtiger.com:8080/job/wiredtiger-pull-request-builds/1875/console

      The file being complained about was added in a different pull request, that isn't yet merged into develop. The git clean -fdqx in our Jenkins jobs aims to leave the git directory in the same state as if it were cleanly cloned. The clean command is currently run from within the build_posix directory in many of our Jenkins jobs - which means it only applies to files underneath build_posix, where it should apply to all files in the cloned tree (documentation here: https://git-scm.com/docs/git-clean).

      We need to fix the jobs so they clean the entire tree, and we should update the Jenkins audit script to catch places where the clean happens from a subdirectory rather than the root.

        Attachments

          Activity

            People

            Assignee:
            david.hows David Hows
            Reporter:
            alexander.gorrod Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: