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

Add option to let the update center connect directly to the update sites

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None

      Description

      Currently the update center needs a client that uses a browser with activated JavaScript (and no blocked sites) to fetch new updates. According to the discussion in the mailing list this seems to be intentional since Jenkins server instances may have no connection to the internet.

      However, it is very confusing for a Jenkins administrator, that the updates depend on the clients JavaScript settings and not on the server settings. There should be at least a note or help text on the corresponding update center page.

      And since there are a lot of Jenkins instances that can connect to the internet, there should be a fallback that tries to use a direct connection from the server to the update sites.

      Isn't a direct connection also used to fetch the tools like maven, jdk, etc.?

        Attachments

          Issue Links

            Activity

            Hide
            bap bap added a comment -

            Can we revert this to the old behaviour - the jenkins server gets the json - and provide an option for those behind firewalls to enable the browser retrieve?

            I do not see why I should allow any site on the internet to run javascript from xmission and osuosl just to enable me to update my Jenkins (or jump through hoops to prevent it)

            IMHO any script referenced by Jenkins should be hosted on that instance of Jenkins. (of cource plugins are free to do what the want - I don't have to use them)

            I'm not even convinced that a Jenkins instance should be asking the browser to contact jenkins-ci.org either, but that one I can live with.

            Show
            bap bap added a comment - Can we revert this to the old behaviour - the jenkins server gets the json - and provide an option for those behind firewalls to enable the browser retrieve? I do not see why I should allow any site on the internet to run javascript from xmission and osuosl just to enable me to update my Jenkins (or jump through hoops to prevent it) IMHO any script referenced by Jenkins should be hosted on that instance of Jenkins. (of cource plugins are free to do what the want - I don't have to use them) I'm not even convinced that a Jenkins instance should be asking the browser to contact jenkins-ci.org either, but that one I can live with.
            Hide
            morgandev Scott Morgan added a comment -

            Agreed. A proxy needs to be configured to download plugins (if the Jenkins server is behind a firewall). The default option should be to have the server connect. An opt in feature would be to use Javascript on the browser to fetch the update.

            Show
            morgandev Scott Morgan added a comment - Agreed. A proxy needs to be configured to download plugins (if the Jenkins server is behind a firewall). The default option should be to have the server connect. An opt in feature would be to use Javascript on the browser to fetch the update.
            Hide
            danielbeck Daniel Beck added a comment -

            Resolved in 1.557 as JENKINS-19081, closing as duplicate.

            Show
            danielbeck Daniel Beck added a comment - Resolved in 1.557 as JENKINS-19081 , closing as duplicate.

              People

              • Assignee:
                Unassigned
                Reporter:
                drulli Ulli Hafner
              • Votes:
                3 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: