[JIRA] [gradle-plugin] (JENKINS-30097) Provide an option for users to decide whether Gradle plugin should transfer sensative environment variables to Gradle command line as jvm system variables or not

[youjenli1...@gmail.com (JIRA)]

Title: Message Title

youjen li updated an issue   Jenkins / JENKINS-30097 Provide an option for users to decide whether Gradle plugin should transfer sensative environment variables to Gradle command line as jvm system variables or not Change By: youjen li Attachment: transferEnvironmentVariables.png By default Gradle build step transfer sensative environment variables to Gradle command line as jvm system variables (-D). However, sometimes it may mix so many environment variables to gradle whether they were needed or not. This could bring out some chance to cause unexpected behavior in complicated build. So I hope jenkins-gradle plugin can provide a build step checkbox option for users to decide whether Gradle plugin should transfer sensative environment variables to Gradle command lne as jvm system variables or not. I have submitted a pull-request to enhance this plugin, please refer to url provided in this issue to review my commit. Thank you~ In order to comply backward compatibility, default value of this option is true. !transferEnvironmentVariables.png|thumbnail! Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.