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 with PHP codesniffer

Haim Paperman

I have a pipeline that installs PHP codesniffer and runs a sniff against my codebase.

When I run this sniff on my server, it outputs all the errors.

When I run this sniff from bitbucket pipelines it fails the entire pipeline after bumping into the first phpcs error.

I would expect it to continue the phpcs script and show all errors and then move on to the next step of my pipeline.

 - step:
    name: PHP CodeSniffer
    caches:
 - composer
 script:
 - set +e
 - composer install
 - vendor/bin/phpcs --standard=PSR2 Api/ Helper/ Model/ Plugin/ Setup/

Accepted answers

All comments

Philip Hodder

Hi Haim,

When Pipelines receives a non-zero exit code, the step and pipeline are marked as failed. It is likely that sniff is returning such an exit code.

Can you attach the error message you're seeing?

You may find using an after-script useful. This will allow you to set up commands that run after the main script has finished. If the command fails the pipeline will still continue. Some testing commands return a non-zero command which may not matter in your pipeline.

Thanks,

Phil

Haim Paperman

@Philip Hodder thanks for the help!

I added an after script, with just an echo, it did the after script but it still didn't go to the next step.

+ vendor/bin/phpcs --standard=PSR2 Api/ Helper/ Model/ Plugin/ Setup/

FILE: ...assian/pipelines/agent/build/Model/System/Message/Podisabled.php
----------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------
33 | WARNING | Line exceeds 120 characters; contains 132 characters
----------------------------------------------------------------------

Time: 60ms; Memory: 6MB

+ echo "after script has run!"
after script has run!
Skipping cache upload for failed step
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.

Philip Hodder

I meant that you should add the phpcs command inside the after script.

Alternatively, you can add the following flag to your phpcs command:

vendor/bin/phpcs --config-set ignore_warnings_on_exit 1 --standard=PSR2 Api/ Helper/ Model/ Plugin/ Setup/

Haim Paperman

@Philip Hodder

Thanks again for your help - real newbie here and I'm really struggling to get it right.
I added the `--config-set ignore_warnings_on_exit 1` flag and it did indeed move on to the next step.

1. The PHPCS step is marked as passed in the pipelines - even though we know it didn't.
I'm guessing that since we told it to ignore warnings so it just marks it as passed.

2. The next step being PHPMD, and I'm back to my original problem. That step failed.

What am I doing wrong?

How can I get a pipeline to run through PHPCS, PHP unit test, PHPMD etc and do all of them in one pipeline and give me the actual results for fail or pass on each step?

Welcome!

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

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines