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

XMLWordPrintable

      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.

        1. transferEnvironmentVariables.png
          transferEnvironmentVariables.png
          130 kB

          [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

          youjen li created issue -
          youjen li made changes -
          Summary Original: Provide an option for users to decide whether Gradle plugin should transfer sensative environment variables to Gradle command lne as jvm system variables or not New: 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
          youjen li made changes -
          Attachment New: transferEnvironmentVariables.png [ 30522 ]
          Description Original: 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.           		New: 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!
          youjen li made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          youjen li made changes -
          Description Original: 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!           		New: 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.

          !transferEnvironmentVariables.png|thumbnail!
          youjen li made changes -
          Description Original: 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.

          !transferEnvironmentVariables.png|thumbnail!           		New: 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.

          !transferEnvironmentVariables.png|thumbnail!

          roger welin added a comment -

          +1 for this one

          roger welin added a comment - +1 for this one
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 165180 ] New: JNJira + In-Review [ 185631 ]
          Stefan Wolf made changes -
          Assignee Original: youjen li [ youjenli ] New: Stefan Wolf [ wolfs ]

          Stefan Wolf added a comment -

          As of Gradle plugin 1.27.1 you can now select not to pass all parameters to the Gradle invocation. If you think this does not fix this issue, please reopen.

          Stefan Wolf added a comment - As of Gradle plugin 1.27.1 you can now select not to pass all parameters to the Gradle invocation. If you think this does not fix this issue, please reopen.
          Stefan Wolf made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Closed [ 6 ]

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

              Created:
              Updated:
              Resolved: