Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29266

install global package don't use default proxy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • nodejs-plugin
    • None
    • centos 6.5

      Hi!
      I found this issue:
      I specified the list of packages to install globally in system configuration of Jenkins
      (Jenkins-configuration-> nodeJS paragraph).
      When a job that use nodeJS is built, the job try to install the package globally but npm doesn't use any proxy configuration (neither jenkins' proxy configuration, neither system proxy environment variables). So, if you under corporate proxy, the installation is not working and ends with ETIMEOUT.

            nfalco Nikolas Falco
            massimone88 Stefano Massimone
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: