Failed to read: jetbrains_powershell_bitness after upgrade to 2023.05
Selecting PowerShell runner and choosing <Auto> for Platform causes exception "Failed to read: jetbrains_powershell_bitness" to be thrown. If x64 or x32 are selected it works fine.
Please sign in to leave a comment.
Hello!
Just gave this a try but, unfortunately, could not reproduce the issue so far. May I ask you to enable debug-general logging preset, reproduce the issue, upload the `teamcity-server.log` file to uploads.jetbrains.com and share the resulting upload ID with me?
Faced same issue today, when powershell build step had Platform: as "Any" build failed with error Failed to read: jetbrains_powershell_bitness. It ran successfully once i selected X64
So *all* our builds with Auto powershell bitness (approx. 1700) started failing with this after upgrade to 2023.05(.3), and seeing as this was the only case I found we decided you were unlikely to do anything about it quickly and bulk updated all the builds through code (versioned settings). However - recently someone added a new build step with Auto (in a template, thus it was only discovered now when a build using the template was run), and that also fails. Yes, I can update it in the template, but this is quite annoying. I struggle to see how you can possibly fail to reproduce this when it happens to every single build step of type jetbrains_powershell on my system…?
Geirbak We ran into multiple powershell problems when we upgraded to different 2023.05.* versions and in our case one problem was related to this bug and it is possible the powershell bitness was as well. https://youtrack.jetbrains.com/issue/TW-82069/The-same-plugin-may-be-loaded-twice-on-agent
When we went under Administration → Plugins we had two instances of ‘PowerShell Runner’ listed, an older version (29898) that said it was not loaded and the new version (129390). We had to completely delete the older version (29898), restart TeamCity, and then everything worked fine after only the newer version (129390) was now being copied down and loaded up on our build agents.
PowerShell Runner, 29898, JetBrains s.r.o., <TeamCity Data Directory>/plugins/teamcity-powershell.zip
Not loaded (Overridden by newer version: powershell-runner[version: 129390, path: [TeamCityPath]\webapps\ROOT\WEB-INF\plugins\.unpacked\powershell])
PowerShell Runner, 129390, JetBrains, <WEB-INF>/plugins/powershell.zip
Support for running PowerShell scripts
Thanks, I haven't seen any other Powershell problems than the bitness one, but I do see we have the exact same situation you describe with PowerShell Runner, 29898, Not loaded and a newer one active. We will also delete the old one.