You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I ran end to end unit test for stencil.js I got this error in bitbucket pipeline. Local it's working properly. Tried multiple way to fix but not able to resolve. please help.
Hi @Pawan Singh and welcome to the community.
Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. If you use a service for a step, then a second Docker container will start for the service which will share a network adapter with your build container. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes these Docker containers get destroyed.
The Docker container where the build is running is a different environment than your local one. You also have a different environment if you use a different Docker image in your bitbucket-pipelines.yml file, as different images have different tools installed.
We have a guide for debugging pipelines builds locally with Docker:
I would suggest following this guide to debug your build locally and see if the issue is reproducible. When debugging locally, please make sure that you use the same Docker images as in your bitbucket-pipelines.yml file instead of the ones mentioned in the guide.
If the issue is reproducible locally, then the error is not specific to Pipelines (it may be related to the Docker image of the build container or your source code). When debugging locally, you can also run additional commands to troubleshoot this further. You could also try debugging it locally with different Docker images.
If you have any questions, please feel free to let me know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.