tag:help.appveyor.com,2012-11-13:/discussions/problems/25118-bash-breaks-between-vs-2017-2019-imagesAppVeyor: Discussion 2020-04-03T18:45:35Ztag:help.appveyor.com,2012-11-13:Comment/477111932019-10-09T18:07:38Z2019-10-09T18:07:38ZBash breaks between VS 2017 -> 2019 images<div><p>Hm, good observation. That's highly possible as there is WSL installed on VS 2019 image and I guess <code>bash</code> command now goes into WSL instead of MSYS as on VS 2017. At the same time removing it from <code>C:\Windows\System32\</code> doesn't sound good... On VS 2017 image it's MSYS running bash by default: <code>C:\msys64\usr\bin\bash.exe</code>.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/477111932019-10-09T18:39:56Z2019-10-09T18:39:56ZBash breaks between VS 2017 -> 2019 images<div><p>Given the option I would use bash from msys over bash from git.</p>
<p>There's more utilities with msys, but I have set the PATH to use bash from git and everything seems as it was</p></div>philip.deegantag:help.appveyor.com,2012-11-13:Comment/477111932019-10-09T19:28:25Z2019-10-09T19:28:25ZBash breaks between VS 2017 -> 2019 images<div><p>Would it be useful if we add built-in support for running bash commands in AppVeyor, with <code>sh:</code> prefix, for instance:</p>
<pre>
<code>build_script:
- sh: echo Call from bash!</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/477111932019-10-09T19:39:31Z2019-10-09T19:39:31ZBash breaks between VS 2017 -> 2019 images<div><p>I think so!</p></div>philip.deegantag:help.appveyor.com,2012-11-13:Comment/477111932019-10-13T22:44:45Z2019-10-13T22:44:45ZBash breaks between VS 2017 -> 2019 images<div><p>This issue has been fixed: <a href="https://github.com/appveyor/ci/issues/3133">https://github.com/appveyor/ci/issues/3133</a></p></div>Feodor Fitsner