The pipeline bat step gets stuck when the workspace path has non-ascii characters

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

XMLWordPrintable

      Since the encoding of the jenkins-wrap.bat script is UTF-8, and the system encoding is GBK, when the workspace path contains non-ascii codes, an error that the path cannot be found will be reported when executed.

            Assignee:
            Unassigned
            Reporter:
            la ku
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: