Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1139

Mirror of node dist and npm registry - and usage of it in plugin-pom

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: artifactory
    • Labels:
      None
    • Similar Issues:

      Description

      from the "misuse of funds" department, plugin builds fail sometimes due to nodejs.org/dist or npm registry being unavailable. 

      One recent case is: https://github.com/nodejs/nodejs.org/issues/1191

      In this case it was the distribution of binaries (node itself) that was unavailable. But often enough the npm registry may be unavailable as well. 

      The parent pom of plugins depends on the frontend-maven-plugin (the latter is NOT a jenkins project)

      The frontend-maven-plugin downloads specified versions of node so that javascript builds can run with the specified version. 

      Unfortunately the parent pom hard codes refrences to both nodejs/dist: 

      https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L1080

       

      And registry.npmjs.org: 

      https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L1094

       

      If INFRA was to offer a mirror of both dist and npm registry (no small ask) then this hard coding could be shifted so builds do not leave the jenkins repo to fetch things they need, vs "external" dependencies. 

       

      cc R. Tyler Croy

       

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                danielbeck Daniel Beck
                Reporter:
                michaelneale Michael Neale
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: