powershell step should hint towards using pwsh step instead

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      powershell executable being replaced by pwsh, one could be confused by the current behaviour because there are two different steps for these different executables.

      If trying to run a powershell step in an environment where it is not available, you get CreateProcess error=2, The system cannot find the file specified.

      If powershell step fails because it could not find the executable, maybe the error message could check whether pwsh is available and hint the user towards using it?

            Assignee:
            Unassigned
            Reporter:
            Vincent Latombe
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: