nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipeline Fail but no useful information about the error

ronwaldo.querol

I have parallel steps - each steps use linux shell runners and execute scripts.

The scripts contains action that pulls the latest code and restarting service.

The script was use in all steps, other step is success and other is fail but on fail steps, the build teardown is same on the successful steps:

Screenshot 2024-02-07 002822.png

I'm using the latest version of pipelines-runner as of today:

atlassian-bitbucket-pipelines-runner-1.559

Accepted answers

Mark C

Hi @ronwaldo.querol,

Welcome to the community.

For your Parallel steps, would you be able to confirm if you're using the same Linux Shell runner?

Also, please be aware of how the Linux Shell runners run your scripts:

Linux Shell Runners use Bash to run pipeline steps on your Linux machine (host device). This allows the runner to execute applications on the host, but does not provide a clean build environment for every step. Any side effects generated by the step (such as, installing any applications, starting a database service, or editing a file outside of the build directory) would potentially affect the next step to be run (including new pipeline runs). To compensate for this, the runner try to empty the build directory empty after each step. It is your responsibility to make sure the scripts you run in each step won’t have a major impact on other steps.

Reference: Set up runners for Linux Shell

Regards,
Mark C

All comments

Mark C

Hi @ronwaldo.querol,

Welcome to the community.

For your Parallel steps, would you be able to confirm if you're using the same Linux Shell runner?

Also, please be aware of how the Linux Shell runners run your scripts:

Linux Shell Runners use Bash to run pipeline steps on your Linux machine (host device). This allows the runner to execute applications on the host, but does not provide a clean build environment for every step. Any side effects generated by the step (such as, installing any applications, starting a database service, or editing a file outside of the build directory) would potentially affect the next step to be run (including new pipeline runs). To compensate for this, the runner try to empty the build directory empty after each step. It is your responsibility to make sure the scripts you run in each step won’t have a major impact on other steps.

Reference: Set up runners for Linux Shell

Regards,
Mark C

ronwaldo.querol

Hi @Mark C - no, each parallel steps use Linux Shell runner but each of them used different workspace runner.

Workspace Runners:

Runner name: my-runner-1

Labels: self.hosted, linux.shell, my-runner-1

Runner name: my-runner-2

Labels: self.hosted, linux.shell, my-runner-2

Where is the build directory located and how we can empty after each step ?

Mark C

Hi @ronwaldo.querol

Are those runners running on the same self-hosted machine?
If yes, you can try using only 1 runner for your parallel steps and see how it goes.

The build directory is usually located from where you started the runners in your self-hosted machine.

Regards,
Mark C

ronwaldo.querol

@Mark C - no, they running on separate host instance.

So our use case is we have separate repository where we store script related to deployment including the script that run linux shell runner.

We created a linux service to start/stop the linux shell runner.

Everytime there is changes on this repository - the pipeline will access every servers(1 server = 1 step) will try to restart the linux shell runner service.

The service is actually restarting, but the status on the pipeline is failed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines