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

[dustinbm@gmail.com (JIRA)]

Dustin McBride created an issue

Jenkins / JENKINS-60151 Ability to specify nodejs version per build Issue Type: Improvement Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2019-11-12 23:26 Priority: Major Reporter: Dustin McBride 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 :  By using the .nvmrc file (this feature is partially supported however if a job does not have a .nvmcr file the build fails  By having the version field accepting a parameter variable  Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[dustinbm@gmail.com (JIRA)]

Dustin McBride updated an issue

Jenkins / JENKINS-60151 Ability to specify nodejs version per build

Change By: Dustin McBride

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 :

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

Add Comment

[dustinbm@gmail.com (JIRA)]

Dustin McBride updated an issue

Jenkins / JENKINS-60151 Ability to specify nodejs version per build Change By: Dustin McBride

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 : #  By using the .nvmrc file (this feature is partially supported however if a job does not have a .nvmcr file the build fails)

#  By having the version field accepting accept a parameter variable

Add Comment

[stronk7@moodle.org (JIRA)]

Eloy Lafuente updated an issue

Jenkins / JENKINS-60151 Ability to specify nodejs version per build

Change By: Eloy Lafuente Attachment: nodejsversion.png

Add Comment

[stronk7@moodle.org (JIRA)]

Eloy Lafuente updated an issue

Jenkins / JENKINS-60151 Ability to specify nodejs version per build

Change By: Eloy Lafuente Attachment: pipeline.png

Add Comment

[stronk7@moodle.org (JIRA)]

Eloy Lafuente commented on JENKINS-60151

Re: Ability to specify nodejs version per build 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 Dustin McBride 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 take rid of the params here if really .nvmrc is supported. Ciao

Add Comment

[stronk7@moodle.org (JIRA)]

Eloy Lafuente edited a comment on JENKINS-60151

Re: Ability to specify nodejs version per build

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.

!nodejsversion.png|thumbnail!  !pipeline.png|thumbnail! 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 take get rid of the params here if really {{.nvmrc}} is supported ) . Ciao :-)

Add Comment