Hi Mike,
Do your Pipelines builds run on Atlassian's infrastructure or are you using one of our self-hosted runners?
If the pipelines builds run on Atlassian's infrastructure or with a self-hosted Linux Docker runner, they use 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. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed.
Builds running with self-hosted Linux Shell, MacOS or Windows Runner run directly on the host machine using Bash (for Linux Shell and MacOS runners) and PowerShell (for Windows runners).
It is not possible to debug the build in Pipelines while it is running. You could debug by adding some additional commands in your yml file to run with the next build.
We have the following guide for debugging a build locally with Docker. This is useful if you want to debug a build running on Atlassian's infrastructure or with a self-hosted Linux Docker runner.
You can try this to see if your build also fails when you debug locally with Docker or if it is successful.
You mentioned that when you run your pipeline manually you don't have this issue, so we would need to see what is different between these two builds.
Does the automated pipeline that fails run on the default, branches, pull-requests, or tags definition?
When you run it manually, do you trigger the pipeline for the same branch/commit as the automated build? And are you selecting the same pipeline definition that failed in the automated run?
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.