My pipeline doesn't work, and i don't know why

[Arnaud Flament]

My pipeline start running and it stop and doesn't push to production.

I have this error: 

php yii_test migrate --interactive=0<1s

1

+ php yii_test migrate --interactive=0

2

3

Warning: require(/opt/atlassian/pipelines/agent/build/common/config/../../vendor/yiisoft/extensions.php): Failed to open stream: No such file or directory in /opt/atlassian/pipelines/agent/build/common/config/base.php on line 5

4

5

Fatal error: Uncaught Error: Failed opening required '/opt/atlassian/pipelines/agent/build/common/config/../../vendor/yiisoft/extensions.php' (include_path='.:/usr/local/lib/php') in /opt/atlassian/pipelines/agent/build/common/config/base.php:5

6

Stack trace:

7

#0 /opt/atlassian/pipelines/agent/build/yii_test(21): require()

8

#1 {main}

9

thrown in /opt/atlassian/pipelines/agent/build/common/config/base.php on line 5

10

Do you have any idea ?

[Theodora Boudale]

Hi Arnaud 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 Docker 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.

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

If the build fails when you reproduce locally with Docker as well, I would suggest reaching out to a php-specific forum for assistance with this error.

Kind regards,
Theodora