Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. 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

      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 no matter they were needed or not. This could bring out chances to cause unexpected behavior in complicated build progress.
      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 line as jvm system variables or not.

      I have submitted a pull-request to enhance this plugin, please refer to the url attached in this issue to review my commit. Thank you~
      In order to comply backward compatibility, default value of this option is true.

          [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

            wolfs Stefan Wolf
            youjenli youjen li
            Votes:
            7 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: