-
Improvement
-
Resolution: Unresolved
-
Major
-
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 :
- 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 accept a parameter variable
[JENKINS-60151] Ability to specify nodejs version per build
Description |
Original:
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 |
New:
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 |
Description |
Original:
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 |
New:
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 accept a parameter variable |
Attachment | New: nodejsversion.png [ 49904 ] |
Attachment | New: pipeline.png [ 49905 ] |