I'm currently working on setting up pipelines for an embedded c project. I've got a working pipeline set up using GCC already but now must set up a similar pipeline using the linux version of iar build tools (bxarm)
I've got a custom docker image set up with all the required software and licenses installed, and a .yml file to load the docker image, and run the iarbuild command. Where I'm getting stuck is that while I can successfully run the intended command in my docker container locally, if I try running the same command in bitbucket my build hangs forever until I kill it.
Can anybody think of a reason why a script would work successfully in a local docker container but not on bitbucket's environment? I'm rather stumped.
See the output from bitbucket pipeline. It almost seems like the command is missing a return key or is waiting on something to continue. I've uploaded a screenshot of what happens when I run the same command on my local docker container.
iarbuild Firmware/platform/lmswdm/lmsw105.ewp -build "Release-For-Bootloader" -log all
IAR Command Line Build Utility V22.214.171.12492/LNX
Copyright 2002-2020 IAR Systems AB.
Building configuration: lmsw105 - Release-For-Bootloader
Updating build tree...
0 file(s) deleted.
Updating build tree...
iccarm /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm/adc.c -D NDEBUG -D BOOTLOADED -D STM32F072 -D USE_STDPERIPH_DRIVER -D HSE_VALUE=3686400 -D LM_DEVICE_TYPE=15 --diag_suppress Pe550 -o /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm/Release-For-Bootloader/Obj --no_cse --no_unroll --no_inline --no_code_motion --no_tbaa --no_clustering --no_scheduling --debug --endian=little --cpu=Cortex-M0 -e --fpu=None --dlib_config /opt/iarsystems/bxarm-8.50.9/arm\inc\c\DLib_Config_Normal.h -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\library\utils/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\library\lmswdm/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\library\lmrc/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\library\irb/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\driver\stm32f0xx/ -I /opt/atlassian/pipelines/agent/build/Firmware/platform/lmswdm\..\..\driver\stm32f0xx\cmsis/ -On --require_prototypes -I /opt/iarsystems/bxarm-8.50.9/arm\CMSIS\Core\Include\ -I /opt/iarsystems/bxarm-8.50.9/arm\CMSIS\DSP\Include\
Here's my .yml file:
Hi @Tyler Jones,
I'm not sure why this issue occurs, we would need to check the build logs to investigate.
Does this repo belong to a workspace on the free plan or a paid plan?
If the repo belongs to a workspace on a paid billing plan, you can create a ticket with the support team to investigate this. You can create a ticket via https://support.atlassian.com/contact/, in "What can we help you with" select "Technical issues and bugs" and then Bitbucket Cloud as product. You can copy-paste the content of your community post in the ticket, and also make sure you provide the URL of the build.
If the repo belongs to a workspace on the free plan, please feel free to let me know and I can create the support ticket for you.
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
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