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

NodeJS Plugin no longer discovers new versions of Node.js

    Details

    • Similar Issues:

      Description

      The NodeJS Plugin no longer updates its list of available Node.js versions. Node.js published three new versions in the last week, 8.9.3, 9.2.1, and 9.3.0, and none of them appear in the plugin's configuration pulldown.

      About five days ago a merged PR for adding SunOS support also included changes to how the plugin does version comparisons:

      https://github.com/jenkinsci/nodejs-plugin/commit/8061a286fce44dec1586233b9ec13349913efe23#diff-1e39583246ee4e60cdcaa0523bd0d40bL62

      These version comparison changes at a quick glance appear unrelated to SunOS support and could be the culprit.

      On a closer look, the version comparison changes look innocuous.

        Attachments

          Issue Links

            Activity

            Hide
            gregcovertsmith Greg Smith added a comment -

            We are also having this problem, with Jenkins 2.73.3 LTS and NodeJS plugin and NodeJS plugin 1.2.4.

             

            I have confirmed that the NodeJS install list that is available here does not include the newer versions of Node:

            https://updates.jenkins.io/current/updates/hudson.plugins.nodejs.tools.NodeJSInstaller.json

             

            I am not sure what generates this file – I assume some kind of backend service that is scanning nodejs.org? 

             

            But in any case, there was a note in the latest LTS release that the url for the update links were changing:

            Default the built-in Jenkins Update Center URL to https://updates.jenkins.io instead of obsolete HTTP endpoint. This requires a JRE compatible with Let's Encrypt, e.g. Oracle JRE 8u101. (pull 2996)

             

            No idea if that is related, just wanted to report.  I've always been able to get new NodeJS releases in the plugin almost immediately after publish, so I feel like some kind of backend process at updates.jenkins.io may have broken down.

            Show
            gregcovertsmith Greg Smith added a comment - We are also having this problem, with Jenkins 2.73.3 LTS and NodeJS plugin and NodeJS plugin 1.2.4.   I have confirmed that the NodeJS install list that is available here does not include the newer versions of Node: https://updates.jenkins.io/current/updates/hudson.plugins.nodejs.tools.NodeJSInstaller.json   I am not sure what generates this file – I assume some kind of backend service that is scanning nodejs.org?    But in any case, there was a note in the latest LTS release that the url for the update links were changing: Default the built-in Jenkins Update Center URL to https://updates.jenkins.io instead of obsolete HTTP endpoint. This requires a JRE compatible with Let's Encrypt, e.g. Oracle JRE 8u101. (pull 2996)   No idea if that is related, just wanted to report.  I've always been able to get new NodeJS releases in the plugin almost immediately after publish, so I feel like some kind of backend process at updates.jenkins.io may have broken down.
            Hide
            nfalco Nikolas Falco added a comment -

            There is an ancient groovy script for each tool plugin that gather information on the tool site and and constructs a JSON file (linked in the previous post for the case of NodeJS) used by plugin to construct the file archive link. This script run (I do not know) weekly? biweekly?

            This pattern is designed by Jenkins and shipped with core library.

            That file is downloaded by your Jenkins instance automatically and when you open the page manage jenkins -> Tools than the combo box is populated with the versions in the JSON file.

            The JSON contains 9.2.0 and 8.9.2, and in my instance I see both 9.2.0 and 8.9.2

             

            New version are not immediatly available.

            Show
            nfalco Nikolas Falco added a comment - There is an ancient groovy script for each tool plugin that gather information on the tool site and and constructs a JSON file (linked in the previous post for the case of NodeJS) used by plugin to construct the file archive link. This script run (I do not know) weekly? biweekly? This pattern is designed by Jenkins and shipped with core library. That file is downloaded by your Jenkins instance automatically and when you open the page manage jenkins -> Tools than the combo box is populated with the versions in the JSON file. The JSON contains 9.2.0 and 8.9.2, and in my instance I see both 9.2.0 and 8.9.2   New version are not immediatly available.
            Hide
            nfalco Nikolas Falco added a comment -

            Any changes not released have no impact on the installed plugin

            Show
            nfalco Nikolas Falco added a comment - Any changes not released have no impact on the installed plugin
            Hide
            gregcovertsmith Greg Smith added a comment -

            I wonder if there is any link or contact info for the parties responsible for running those scripts in the Jenkins organization.

            Looking at the file dates on https://updates.jenkins.io/current/updates/ – it appears that the groovy scripts mentioned have not been run since December 6th, 2017.  All of them (including NodeJS's data file) have the same date.

            So the data there is 9 days old – thinking they probably do run those weekly, then something has happened, if they run them every other week, then maybe its in spec...

            I will say something in the google group here:https://groups.google.com/forum/?nomobile=true#!forum/jenkinsci-users

            as I don't know where else to announce or ask for such information...

            Show
            gregcovertsmith Greg Smith added a comment - I wonder if there is any link or contact info for the parties responsible for running those scripts in the Jenkins organization. Looking at the file dates on https://updates.jenkins.io/current/updates/ – it appears that the groovy scripts mentioned have not been run since December 6th, 2017.  All of them (including NodeJS's data file) have the same date. So the data there is 9 days old – thinking they probably do run those weekly, then something has happened, if they run them every other week, then maybe its in spec... I will say something in the google group here: https://groups.google.com/forum/?nomobile=true#!forum/jenkinsci-users as I don't know where else to announce or ask for such information...
            Hide
            gregcovertsmith Greg Smith added a comment -

            Through the forum, Daniel Beck graciously pointed me to INFRA-1428 as the root cause of the issue.

            Show
            gregcovertsmith Greg Smith added a comment - Through the forum, Daniel Beck graciously pointed me to INFRA-1428 as the root cause of the issue.
            Hide
            pe8ter Peter Safranek added a comment -

            I can confirm that the Jenkins background job that populates the NodeJS Plugin's Node.js version list works again. Thanks to those that helped suss out the deeper problem.

            Show
            pe8ter Peter Safranek added a comment - I can confirm that the Jenkins background job that populates the NodeJS Plugin's Node.js version list works again. Thanks to those that helped suss out the deeper problem.

              People

              • Assignee:
                nfalco Nikolas Falco
                Reporter:
                pe8ter Peter Safranek
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: