Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

windeployqt executable suddenly couldn't detect os platform and not reproducible outside bamboo jvm Edited

Getting strange errors using msbuild, consistently on every different bamboo build for every executable project on every single commit this week. I cannot reproduce it and would like help reproducing it.


  • I've ran the same build task on code that was rolled back to successful builds from bamboo, disabling checkout and auto-deleting.
  • I've built the bamboo generated sln, in visual studio
  • I've built the code with cmake --build locally in the same location as the bamboo plan
  • I've built the code with the same msbuild executable locally in the same location as the bamboo plan with the same configs specified in the task
  • I've fiddled with the msbuild configuration in bamboo
  • I got bamboo to ouput the os version from it's jvm to see if it was weirdness with windows/linux

Nothing is running concurently as far as I know so it shouldn't be resource issue. Building c++ x64 vc14 and using cmake

Everything I've done so far has built with no errors.


Some of the bamboo errors including

EXEC : warning : --pdb is not supported on this platform. <youdontnee'dtoknowmyfilestructure>.vcxproj] build 04-Sep-2017 15:42:19 Unable to query qmake: Error creating stdout temporary file
: error MSB3073: <youdon'tneedtoknowmyfilestructure>qt-5.7.0\bin\windeployqt.exe --no-translations --no-compiler-runtime 

 and then because of that, running executables produced by a bamboo build fail because they can't find qt dlls.


Ideas on how to reproduce or why it fails.

1 answer

The localSystem account didn't have read/write permissions on c:/windows/temp which is the account that runs the bamboo service. The temp dir was also very full so the executable tried and failed to create tempory files because they were already there.


solution was just to change permissions for localsystem and clear temp dir

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center - Early Access Program 2

We’re preparing for Bamboo 8.0, which will be our first Data Center release. To make sure our app vendors and customers with written in-house apps are prepared, we’re launching Bamboo 8.0 Early Acces...

132 views 1 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you