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

Null Error When Downloading Plugins

    Details

    • Sprint:
      GSoC 2019. Coding Phase 2, GSoC 2019. Coding Phase 3
    • Similar Issues:

      Description

      The following error was encountered: 

      The command '/bin/sh -c mkdir -p $jenkins_home/plugins && cat $jenkins_home/plugins.txt && java -jar $jenkins_home/install-plugins.jar --plugin-file $jenkins_home/plugins.txt' returned a non-zero code: 1

      https://gist.github.com/casz/92b43e9ba4f994114b01d6ae9dc73b10

       

       

        Attachments

          Issue Links

            Activity

            Hide
            stopalopa Natasha Stopa added a comment -

            After investigating, it turned out that there were a couple of related errors:

            The first is that if the dependency info can’t be parsed from the https://updates.jenkins.io/current/plugin-versions.json, it’s parsed from the manifest. I assumed that the "Plugin-Dependencies” field would always be present in the manifest, but apparently this is not the case. This caused a null pointer error and the “null” output string that was being seen earlier.

            The second, related issue is that the reason the dependency information was unable to be parsed from the plugins-versions.json was because the requested plugin who dependency info failed was the "node-iterator-api” plugin (needed for the vsphere-cloud he requested) and the plugin-versions.json has dependency information for version 1.5.0, but the version of node-iterator-api that was requested was 1.5, which the tool current views as not equivalent. I had created a Jira task for a similar issue a while back: https://issues.jenkins-ci.org/browse/JENKINS-58537

            Show
            stopalopa Natasha Stopa added a comment - After investigating, it turned out that there were a couple of related errors: The first is that if the dependency info can’t be parsed from the https://updates.jenkins.io/current/plugin-versions.json , it’s parsed from the manifest. I assumed that the "Plugin-Dependencies” field would always be present in the manifest, but apparently this is not the case. This caused a null pointer error and the “null” output string that was being seen earlier. The second, related issue is that the reason the dependency information was unable to be parsed from the plugins-versions.json was because the requested plugin who dependency info failed was the "node-iterator-api” plugin (needed for the vsphere-cloud he requested) and the plugin-versions.json has dependency information for version 1.5.0, but the version of node-iterator-api that was requested was 1.5, which the tool current views as not equivalent. I had created a Jira task for a similar issue a while back: https://issues.jenkins-ci.org/browse/JENKINS-58537
            Show
            stopalopa Natasha Stopa added a comment - First issue fixed in:  https://github.com/jenkinsci/plugin-installation-manager-tool/pull/50
            Hide
            stopalopa Natasha Stopa added a comment -

            Closing this issue. Will track fix for second part in JENKINS-58537.

            Show
            stopalopa Natasha Stopa added a comment - Closing this issue. Will track fix for second part in  JENKINS-58537 .

              People

              • Assignee:
                stopalopa Natasha Stopa
                Reporter:
                stopalopa Natasha Stopa
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: