Hello. I did bump into a bug I can figure out. Would be glad for any help.
I have a pipeline configured like this:
# You can specify a custom docker image from Docker Hub as your build environment.
- composer build-dev
- php --version
- composer --version
- phpunit --version
- phpunit -c phpunit.xml --debug
A proper configuration phpunit.xml file that works on a local environment just fine. But when the pipeline runs phpunit always returns 0 when running the tests. Same goes for running with --testdox attribute.
Here is the phpunit.xml
<?xml version="1.0" encoding="UTF-8"?>
Tried everything I could imagine and (even local phpunit/phpunit docker image to debug and it behaves the same).
My bad, that was the application issue and it is not related with bitbucket, pipeline or phpunit. I suppose there is no option to remove the question? If so I will at least explain what caused it. If application quit in any point of the execution for example with die() or exit() and the status is 0 (which is by default) pipeline will detect it as a success. So if you're having the same issue, just try to detect where script stops with for eg. register_shutdown_function()
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs