[JIRA] (JENKINS-60720) Possibility to specify if env variables should be filtered or not in npm config file

[and...@hammar.net (JIRA)]

Title: Message Title

Anders Hammar created an issue   Jenkins / JENKINS-60720 Possibility to specify if env variables should be filtered or not in npm config file Issue Type: Improvement Assignee: Nikolas Falco Components: nodejs-plugin Created: 2020-01-10 07:34 Priority: Major Reporter: Anders Hammar In a npm configuration file any environment variable (specified by $VARIABLE_NAME or ${VARIABLE_NAME}) is being filtered/replaced by the env varibale value. If the filtering process can't find the env varibale an error message is logged in the build console. However, in some cases it would be desirable to keep the "${VARIABLE_NAME}" string in the used npm config file so that npm itself replaces this. One scenario is for authentication, like this: registry=http://nexus.acme.org/repository/npm-group/ //nexus.acme.org/repository/npm-releases/:_authToken=\${NPM_TOKEN} In this case, for security reasons, you don't want the env variable to be expanded/filtered during the copying of the config file but rather have npm fetching the env variable value during the "npm publish" execution. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203969.1578641690000.6069.1578641700693%40Atlassian.JIRA.