1. 08 Sep, 2015 1 commit
    • Disable the pip version check message · 0dea5605
      This message is being shown to people who should not be deciding whether
      to upgrade pip, so it is just confusing and alarming noise.
      
      Before:
      
      ---> pavelib.prereqs.install_prereqs
      ---> pavelib.prereqs.install_ruby_prereqs
      Ruby prereqs unchanged, skipping...
      ---> pavelib.prereqs.install_node_prereqs
      Node prereqs unchanged, skipping...
      ---> pavelib.prereqs.install_python_prereqs
      pip install -q --exists-action w -r requirements/edx/pre.txt
      You are using pip version 6.0.8, however version 7.1.2 is available.
      You should consider upgrading via the 'pip install --upgrade pip' command.
      pip install -q --exists-action w -r requirements/edx/github.txt
      You are using pip version 6.0.8, however version 7.1.2 is available.
      You should consider upgrading via the 'pip install --upgrade pip' command.
      Could not find a tag or branch '96e1922348bfe6d99201b9512a9ed946c87b7e0b', assuming commit.
      Could not find a tag or branch 'b0686a76f1ce3532088c4aee6e76b9abe61cc808', assuming commit.
      Could not find a tag or branch '88ec8a011e481918fdc9d2682d4017c835acd8be', assuming commit.
      
      After:
      
      ---> pavelib.prereqs.install_prereqs
      ---> pavelib.prereqs.install_ruby_prereqs
      Ruby prereqs unchanged, skipping...
      ---> pavelib.prereqs.install_node_prereqs
      Node prereqs unchanged, skipping...
      ---> pavelib.prereqs.install_python_prereqs
      pip install -q --disable-pip-version-check --exists-action w -r requirements/edx/pre.txt
      pip install -q --disable-pip-version-check --exists-action w -r requirements/edx/github.txt
      Could not find a tag or branch '96e1922348bfe6d99201b9512a9ed946c87b7e0b', assuming commit.
      Could not find a tag or branch 'b0686a76f1ce3532088c4aee6e76b9abe61cc808', assuming commit.
      Could not find a tag or branch '88ec8a011e481918fdc9d2682d4017c835acd8be', assuming commit.
      Ned Batchelder committed
  2. 06 Aug, 2015 1 commit
  3. 30 Jul, 2015 2 commits
  4. 15 Jul, 2015 1 commit
  5. 14 Jul, 2015 1 commit
  6. 09 Jul, 2015 1 commit
  7. 12 Jan, 2015 1 commit
  8. 31 Dec, 2014 2 commits
  9. 21 Nov, 2014 1 commit
  10. 20 Aug, 2014 1 commit
    • Check for npm registry and set it if necessary. · b2482f54
      If paver is being run by a user that is not the same as the user
      that installed npm on the guest machine, then paver install_prereqs fails
      with the following error:
      
        ---> pavelib.prereqs.install_node_prereqs
        npm config set registry http://registry.npmjs.org/
        npm ERR! Error: EPERM, chown '/home/jenkins/.npmrc'
        npm ERR!  { [Error: EPERM, chown '/home/jenkins/.npmrc'] errno: 50, code: 'EPERM', path: '/home/jenkins/.npmrc' }
        npm ERR!
        npm ERR! Please try running this command again as root/Administrator.
      
        npm ERR! System Linux 3.2.0-23-generic
        npm ERR! command "/usr/bin/node" "/usr/bin/npm" "config" "set" "registry" "http://registry.npmjs.org/"
        npm ERR! cwd /home/jenkins/shallow-clone
        npm ERR! node -v v0.10.30
        npm ERR! npm -v 1.4.21
        npm ERR! path /home/jenkins/.npmrc
        npm ERR! code EPERM
        npm ERR! errno 50
        npm ERR! stack Error: EPERM, chown '/home/jenkins/.npmrc'
        npm ERR!
        npm ERR! Additional logging details can be found in:
        npm ERR!     /home/jenkins/shallow-clone/npm-debug.log
        npm ERR! not ok code 0
      
        Captured Task Output:
        ---------------------
      
        ---> pavelib.prereqs.install_prereqs
        ---> pavelib.prereqs.install_ruby_prereqs
        ---> pavelib.prereqs.install_node_prereqs
        npm config set registry http://registry.npmjs.org/
      
        Build failed running pavelib.prereqs.install_prereqs: Subprocess return code: 50
      
      This change is a workaround. It will first see if the value is set. In the case
      that is it not set, it will attempt to set it. (It will then fail; however,
      re-running the task will subsequently be successful.)
      Ben Patterson committed
  11. 20 Jun, 2014 1 commit
  12. 18 Jun, 2014 1 commit
  13. 14 Jun, 2014 1 commit
  14. 13 Jun, 2014 1 commit
  15. 02 Jun, 2014 1 commit
  16. 23 May, 2014 2 commits
  17. 20 May, 2014 1 commit
  18. 28 Apr, 2014 1 commit
  19. 02 Apr, 2014 1 commit
  20. 31 Mar, 2014 1 commit
  21. 28 Mar, 2014 1 commit
  22. 25 Mar, 2014 2 commits
  23. 24 Feb, 2014 1 commit
  24. 18 Feb, 2014 1 commit
  25. 14 Feb, 2014 2 commits