1. 19 Mar, 2014 4 commits
  2. 07 Mar, 2014 1 commit
    • Petr Pudlak's avatar
      Add patching QA configuration files on buildbots · b7630577
      Petr Pudlak authored
      In order to work, it is necessary:
      * Write a JSON Patch to file "qa/qa-patch.json" in a source repository.
        (And be careful not to commit it!) The file must conform to RFC6902
        and describes what changes should be done to the QA JSON
        configuration. This is simple as
           { "op": "add",
             "path": "default",
             "value": false },
           { "op": "add",
             "path": "/tests/instance-add-file",
             "value": true }
      * Install "jsonpatch" and "jsonpointer" modules on the machines QA is
        running on. Either using "easy_install" or as Debian packages using
      QA only loads the modules if the patch file is present and non-empty.
      Therefore no changes to buildbots are needed, if the feature is not
      It's advisable to add a git pre-commit hook for the main repository to
      prevent changes to "qa/patch.json", keeping it to "[]". Suggestion for
      such a hook:
        # Exit code 1 if the patch file isn't just "[]":
        python -c 'import json, sys; \
          exit(0 if json.load(open("qa/qa-patch.json", "r")) == [] else 1)'
      Locally it's possible to tell git not to track changes to the file at
      all (see https://help.github.com/articles/ignoring-files):
        git update-index --assume-unchanged qa/qa-patch.json
      Cherry-pick of e5398c3a
       from stable-2.11.
      Signed-off-by: default avatarPetr Pudlak <pudlak@google.com>
      Signed-off-by: default avatarMichele Tartara <mtartara@google.com>
      Reviewed-by: default avatarJose A. Lopes <jabolopes@google.com>
  3. 25 Sep, 2013 1 commit
  4. 29 Jul, 2013 1 commit
  5. 23 Jul, 2013 1 commit
  6. 15 Jul, 2013 1 commit
  7. 23 May, 2013 1 commit
  8. 26 Apr, 2013 1 commit
  9. 17 Apr, 2013 1 commit
  10. 14 Apr, 2013 1 commit
  11. 11 Apr, 2013 1 commit
  12. 21 Mar, 2013 1 commit
  13. 27 Feb, 2013 2 commits
  14. 20 Feb, 2013 4 commits
  15. 12 Feb, 2013 2 commits
  16. 11 Feb, 2013 3 commits
  17. 08 Feb, 2013 6 commits
  18. 04 Feb, 2013 1 commit
  19. 01 Feb, 2013 5 commits
  20. 03 Sep, 2012 1 commit
    • Iustin Pop's avatar
      Fix warnings/errors with newer pylint · 8ad0da1e
      Iustin Pop authored
      To help developing Ganeti on newer distributions, let's try to fix
      pylint warnings/errors. I'm using pylint from current Debian wheezy:
      pylint 0.25.1, astng 0.23.1, common 0.58.0, and we have 3 things that
      needs fixing.
      First, a really wide "except", with the silencing in the wrong
      place. I'm not sure why this doesn't have "except Exception", so let's
      add it. However, pylint still complains about "Catching too general
      exception", even though we do want to catch both system and our
      exception, so let's add a silence for W0703. It's true that we
      shouldn't catch KeyboardInterrupt and friends, but that should be
      cleaned up on the master branch.
      Second, pylint complains about "redefining name builtin tuple",
      because we do some pattern matching in the except blocks in
      netutils. This seems to be a false positive, but let's clean the code
      around this.
      And finally, type inference again goes bad, so let's silence E1103
      with its "boolean doesn't have 'get' method".
      After this, I can run "make lint", and by extension "make
      commit-check" on Debian Wheezy, yay! We might be able to bump our
      required pylint versions to something not ancient…
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
  21. 15 Jun, 2012 1 commit