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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Bamboo Build Plans failing with compilation errors

Our bamboo build plan was setup on Windows 7 earlier and worked completely fine. Then, we moved the same build plan to a windows 10 based PC, that is when the builds started failing.

We are using ti based Code Composer Studio 6 with C6000 and arm compilers. We have ruled out any issues with Code composer and ti based products as outside the bamboo environment, the binaries and builds are getting created succesfully on Windows 10.

Attached is the error log. It seems like bamboo is not able to access some files in our remote server and hence the builds are failing. My questions is are there any known issues related to bamboo integration with Windows 10? Or has anyone seen the attached error before?



1 answer

0 votes
jira guy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 16, 2019

Error messages are clear. You are missing some files that are in windows 7 and not in 10. Search for those files and move them to same path in the new server

So the thing is that the file mentioned here is apparently some temp file getting created somewhere. Its not an actual file that exists in our project. And every time we run the build plan, there is some new numbered file that shows up in the log.

command file '\\0352014')

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events