Pipeline failing due to atlassian classes not found issue

Bhavani Ramalingan

 

"composer validate --no-check-all --ansi in /opt/atlassian/pipelines/agent/build"

above command failed due to the classes are not found. 

 

<span>In AutoloadGenerator.php line 1396:</span>

<span>require(/opt/atlassian/pipelines/agent/build/docroot/core/includes/bootstra</span><span>p.inc): Failed to open stream: No such file or directory.</span>

 

Theodora Boudale

Hi Bhavani 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. 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.

Build errors may be related to your source code, any dependencies you use, or the Docker image you use as a build container. You can narrow down whether this is a pipelines-specific issue by reproducing the build locally with Docker, using the following guide:

• https://confluence.atlassian.com/bbkb/troubleshoot-failed-bitbucket-pipelines-locally-with-docker-1318882094.html

Just make sure you replace the path /opt/atlassian/pipelines/agent/build in the command with the path where your repo's clone exists in the local Docker container. If the build fails when you rerproduce locally with Docker as well, then the issue is not specific to Pipelines. You'll need to debug this further until you have a build that succeeds locally, so it can also run on Pipelines.

Kind regards,
Theodora