Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,003
Community Members
 
Community Events
168
Community Groups

Bitbucket Pipeline getting stuck

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 V8.4.11.7092/LNX
Copyright 2002-2020 IAR Systems AB.
Building configuration: lmsw105 - Release-For-Bootloader
Updating build tree...
0 file(s) deleted.
Updating build tree...
adc.c
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:
# This is a build configuration for GCC and Make.
# Guides are at https://confluence.atlassian.com/x/5Q4SMw
# Only use spaces to indent your .yml configuration.
# -----
# Specify a custom docker image from Docker Hub as your build environment.
image:
name: #hide this secret
username: #hide this secret
password: #####not shown
email: tyler.jones@legrand.us
clone:
depth: 6
options:
size: 2x
pipelines:
default:
- parallel:
- step:
name: Build ARM LMSWDM
script:
# configure the build environment
- iarbuild Firmware/platform/lmswdm/lmsw105.ewp -clean "Release-For-Bootloader" -log all
- iarbuild Firmware/platform/lmswdm/lmsw105.ewp -build "Release-For-Bootloader" -log all
#- apt-get install --quiet --assume-yes gcc-arm-none-eabi
# main repo is already cloned, but sub-repos are not cloned yet
# - git submodule sync --recursive
# - git submodule update --recursive --init --force
# projects to build
# - make lmswdm-st
Capture.PNG

1 answer

0 votes

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.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,503 views 3 10
Read article

Atlassian Community Events