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

Ability to specify nodejs version per build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • nvm-wrapper-plugin
    • None

      We have several javascript and java projects that share one job. Several of the javascript projects use different versions of node. It would be nice if we could specify the version of node per build. This could be accomplished by either :

      1.  By using the .nvmrc file (this feature is partially supported however if a job does not have a .nvmcr file the build fails)
      2.  By having the version field accept a parameter variable 

        1. nodejsversion.png
          nodejsversion.png
          17 kB
        2. pipeline.png
          pipeline.png
          13 kB

          [JENKINS-60151] Ability to specify nodejs version per build

          Eloy Lafuente added a comment - - edited

          Hi,

          I was looking about which is the current support for .nvmrc files in the plugin and arrived here. And now I'm confused (twice):

          1. What does mean that .nvmrc "feature is partially supported" ? Is it supported or no?
          2. I think it's already possible to define the nodejs version via param and then use it, at very least in pipelines. Here we have this and, so far, it's working ok.

          Hope that suits (maybe) your needs dustinbm

          And then, now I'm confused which "lts/carbon" we are getting installed (the explicit one passed as param or the one specified in our .nvmrc file. I would expect the explicit one to get precedence over the default one, in fact we added the .nvmrc recently and jobs are older than that.

          So it would be great to know about 1) above and know the order of precedence (just aiming to get rid of the params here if really .nvmrc is supported).

          Ciao

          Eloy Lafuente added a comment - - edited Hi, I was looking about which is the current support for .nvmrc files in the plugin and arrived here. And now I'm confused (twice): 1. What does mean that .nvmrc "feature is partially supported" ? Is it supported or no? 2. I think it's already possible to define the nodejs version via param and then use it, at very least in pipelines. Here we have this and, so far, it's working ok. Hope that suits (maybe) your needs dustinbm And then, now I'm confused which "lts/carbon" we are getting installed (the explicit one passed as param or the one specified in our .nvmrc file. I would expect the explicit one to get precedence over the default one, in fact we added the .nvmrc recently and jobs are older than that. So it would be great to know about 1) above and know the order of precedence (just aiming to get rid of the params here if really .nvmrc is supported). Ciao

            atoms Tomas Salazar
            dustinbm Dustin McBride
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: