• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Jenkins 2.241

      SimpleBuildStep.perform needs to be given an EnvVars argument. Otherwise there is no way for an implementation to observe any local environment variable settings.

          [JENKINS-29144] SimpleBuildStep to receive EnvVars

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-23713 [ JENKINS-23713 ]

          Jesse Glick added a comment -

          A way for the step to set variables has also been requested. In a freestyle build I suppose this would simply set build variables. In a Pipeline build, not sure. Return a Map<String,String> from step?

          Jesse Glick added a comment - A way for the step to set variables has also been requested. In a freestyle build I suppose this would simply set build variables. In a Pipeline build, not sure. Return a Map<String,String> from step ?
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164012 ] New: JNJira + In-Review [ 181474 ]
          Andrew Bayer made changes -
          Labels Original: workflow New: pipeline workflow
          Andrew Bayer made changes -
          Labels Original: pipeline workflow New: pipeline

          Jesse Glick added a comment -

          In a freestyle build I suppose this would simply set build variables.

          Or via EnvironmentContributingAction, which is also not an option for a SimpleBuildStep due to JENKINS-29537.

          Jesse Glick added a comment - In a freestyle build I suppose this would simply set build variables. Or via EnvironmentContributingAction , which is also not an option for a SimpleBuildStep due to JENKINS-29537 .
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-29537 [ JENKINS-29537 ]

          Jesse Glick added a comment -

          Without JENKINS-40070Run.getEnvironment cannot be used as a workaround.

          Jesse Glick added a comment - Without  JENKINS-40070 ,  Run.getEnvironment cannot be used as a workaround.
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-40070 [ JENKINS-40070 ]

            zastai Tim Van Holder
            jglick Jesse Glick
            Votes:
            3 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: