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

Bitbucket pipline fails on yarn install when switch to bitbucket Runner

Uladzislau Ramanchanka
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2023

Hello, folks!

When we have switched to bitbucket Runner mechanism our pipline started failing and thrown an error on yarn install:

yarn.PNG

when we use size: 2x memory instead of using bitbucket runner there is no error. 
Will appreciate any support!
Thanks!

 

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 19, 2023

Hi Uladzislau and welcome to the community!

Could you please let me know what type of Runner are you using? Is it a Linux Docker, Linux Shell, MacOS, or Windows Runner?

What is the operating system of the host machine this runner is running?

Kind regards,
Theodora

Uladzislau Ramanchanka
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 20, 2023

Hello, Theodora
this is MacOs runner thus OS is MacOs
Best regards, Uladzislau

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 20, 2023

Hi Uladzislau,

Thank you for your reply.

Just to give you some context, Pipelines builds that run on Atlassian infrastructure use Docker containers. For every step of your build, a Docker container starts using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in that container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.

MacOS Runners do not use Docker containers. They use Bash to run pipeline steps on your MacOS machine (host device). This allows the runner to execute applications on the host but does not provide a clean build environment for every step.

I would suggest running the build on this Mac without using a runner:

  • clone the repo on this Mac from a terminal
  • do a git reset --hard to the commit that this Pipelines build is running for
  • then execute the commands of the build inside the clone directory and see if yarn install shows the same error or if it succeeds

This is to narrow down whether the issue seems to be related to the runner or to running the build on this Mac.

If you want an environment similar to the one on Atlassian infrastructure and you have a Linux machine, you could use a Linux Docker Runner instead, which uses Docker containers for each step.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events