Pipeline builds on Windows Runner displaying garbage data on the build logs or artifacts
プラットフォームについて: Cloud のみ - この記事は クラウド プラットフォームのアトラシアン製品に適用されます。
要約
When executing builds in Bitbucket Pipelines Runners for Windows, it is possible to encounter a scenario in which the build logs or artifacts produced by the build appear jumbled or unreadable.
For example, when trying to run the following command in Pipelines running on Windows Runner:
echo "┌─"You may see broken characters on the build logs, like this:
echo "�"O�"?�"環境
Bitbucket Pipelines Windows Runners.
診断
Try executing the same build or affected command in an alternative Runners architecture, such as Linux Runners.
Should you observe a different outcome, it is probable that this variation is connected to the issue outlined in this article.
Conversely, if the problem persists, it is likely associated with the command you are utilizing, rather than the issue discussed in this article. In such instances, it is advisable to reach out to the maintainers of the package that is causing the problem.
原因
Your Windows machine may not be configured to support Unicode UTF-8, which can result in its inability to process Unicode characters during the execution of your build. Proper configuration is essential for ensuring that your system can handle a wide range of characters effectively.
ソリューション
To address this issue, it is required to enable support for Unicode UTF-8 on Windows machine. The following steps outline the procedure to accomplish this:
On the Windows machine, access the Windows settings and proceed to the "Region & Language" page.
Select "Administrative Language Settings" located in the right corner of the configuration page.
A new dialog box will appear. Click on the "Change system locale..." button.
Another dialog box will open. In this new dialog, you will find a checkbox labeled "Beta: Use unicode UTF-8 for worldwide language support." Ensure that this checkbox is selected, and then click "OK."
- Please restart the Windows machine and the Windows Runner
Should the problem continue after implementing the above steps, please contact support, or engage with the Atlassian community.