Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34581

Please add support for Pipelines to the Powershell plugin

XMLWordPrintable

      I would like to use the powershell plugin from within pipelines, please add support for the pipelines to the powershell plugin.

      This is especially important as we approach Jenkins 2.0 and its move towards pipelines.

        1. input.png
          input.png
          3 kB
        2. result.PNG
          result.PNG
          9 kB

          [JENKINS-34581] Please add support for Pipelines to the Powershell plugin

          Stuart Whelan created issue -
          Patrick Wolf made changes -
          Labels Original: microsoft pipeline powershell windows New: microsoft pipeline powershell windows workflow

          Andrew Bayer added a comment -

          It'd be really great to get real Pipeline integration, a la sh and bat - i.e., a DurableTaskStep implementation for Powershell.

          Andrew Bayer added a comment - It'd be really great to get real Pipeline integration, a la sh and bat - i.e., a DurableTaskStep implementation for Powershell.

          Jesse Glick added a comment -

          For now you should use the bat step with powershell.exe. Making Powershell be a SimpleBuildStep is a bad idea.

          Jesse Glick added a comment - For now you should use the bat step with powershell.exe . Making Powershell be a SimpleBuildStep is a bad idea.
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-26055 [ JENKINS-26055 ]
          James Nord made changes -
          Component/s New: durable-task-plugin [ 18622 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 170734 ] New: JNJira + In-Review [ 184018 ]
          Andrew Bayer made changes -
          Labels Original: microsoft pipeline powershell windows workflow New: microsoft pipeline powershell windows

          Clint Chapman added a comment -

          jglick, Bad idea because?

          Clint Chapman added a comment - jglick , Bad idea because?

          Jesse Glick added a comment -

          Because it would not be durable.

          The choices are:

          • use JENKINS-37011 to provide something that looks for purposes of Snippet Generator and script syntax like a regular step, but which really just calls bat with some wrapper code
          • implement a first-class FileMonitoringTask that bypasses *.bat entirely

          Jesse Glick added a comment - Because it would not be durable. The choices are: use JENKINS-37011 to provide something that looks for purposes of Snippet Generator and script syntax like a regular step, but which really just calls bat with some wrapper code implement a first-class FileMonitoringTask that bypasses *.bat entirely

            gabloe Gabriel Loewen
            stuartwhelan Stuart Whelan
            Votes:
            40 Vote for this issue
            Watchers:
            51 Start watching this issue

              Created:
              Updated:
              Resolved: