You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Controlling how environment variables are exposed
As shown in the example above, you can control which environment variables are exposed in clientConfig.setIncludeEnvVars using clientConfig.setEnvVarsExcludePatterns and clientConfig.setEnvVarsIncludePatterns. These calls specify which environment variables should be excluded or included respectively using a parameter which is a comma-separated list of expressions to exclude or include. The expressions can use a star ('*') wildcard to specify multiple environment variables."
After enabling this flag I tried various voodoo ways to populate variables with 0 effect:
Same as gradle devs, same artifactory plugin devs seems to be lost in their own worlds.
According to source code:
public void setIncludeEnvVars(Boolean enabled) {
rootConfig.setBooleanValue(INCLUDE_ENV_VARS, enabled);
}
Nothing to do with System.getenv(propertyName) which anyone else would believe it's doing. So you can only pass -D parameter style and not environmental variable to configure artifactory plugin.
https://www.jfrog.com/confluence/display/JFROG/Gradle+Artifactory+Plugin
"Controlling how environment variables are exposed
As shown in the example above, you can control which environment variables are exposed in clientConfig.setIncludeEnvVars using clientConfig.setEnvVarsExcludePatterns and clientConfig.setEnvVarsIncludePatterns. These calls specify which environment variables should be excluded or included respectively using a parameter which is a comma-separated list of expressions to exclude or include. The expressions can use a star ('*') wildcard to specify multiple environment variables."
After enabling this flag I tried various voodoo ways to populate variables with 0 effect:
???
The text was updated successfully, but these errors were encountered: