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!


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
Community Members
Community Events
Community Groups

ELI5 bitbucket pipelines. Error when running eslint on the project


Hi there, I'm trying to better  understand  how do pipelines actually work.

I'm guessing a docker image is created for each step on the pipeline, or is it just a single docker image?


I'm trying to hook a pipeline with an ubuntu server so it can deploy my react-app on every merge to `master`. The pipeline sort of works, but when there are some steps tha fail.

1. `eslint`

2. `test`


Here is my config:





1 answer

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 24, 2021

Hi @DS ,

For each step of a pipeline, new Docker container starts, the repo is cloned in this container and then the commands of the script are executed.

If you define an image at the beginning of your bitbucket-pipelines.yml file, like in your screenshot, this image will be used for every step.

However, it is also possible to specify a different image for each step, an example from our docs for that is as follows:

- step:
name: Build and test
image: node:10.15.0
- npm install
- npm test
- npm run build
- dist/**
- step:
name: Deploy
image: python:3.7.2
trigger: manual
- python

It's a bit difficult to say why the errors occur without seeing any log info. Could you perhaps let us know:

  1. Which steps are failing from your bitbucket-pipelines.yml file, and specifically which command fails for each step?
  2. Could you share the output of these commands here, sanitizing any private/sensitive data in the output?

Kind regards,

Hi @Theodora Boudale I think the problem might be on how i'm structuring my repo ?  I need to test this, but let me know what you think.

Right now the command that fails is 


 - step:
name: Running the linter
- yarn run lint # [Error]: Unable to follow eslint

Right now my folder structure is 


website # where al the code for the app is found including package.json


I think I should tell the pipeline to first go to `website`  and the run all the commands? 

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 29, 2021

Hi @DS ,

When you run a Pipelines build, a Docket container starts, then the branch is cloned in that Docker container (if it's a build running on a branch) and the commands of the script are executed in the directory of that clone.

If this command needs to run in the directory where you have your source, this might indeed be the culprit.

What you can do is add an extra command to switch to this directory first:

- step:
name: Running the linter
- cd website
- yarn run lint

Could you give this a try and let me know how it goes?

Kind regards,

Like DS likes this

@Theodora Boudale never managed to answer you, but   everything running smoothly now. Thanks

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 09, 2022

Hi @DS,

Thank you for the update, that's good to hear and you are very welcome!

Please feel free to reach out if you ever need anything else.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events