Codecov not ignoring files specified in codecov.yaml

Before submitting a topic, please confirm the following

I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my codecov.yaml configuration file.
I have filled out the below sections to the best of my ability.
I understand that the community boards are a free, best-effort tool. While we hope to have someone on the Codecov team resolve your problem quickly, this is not always possible.



I’m using CodeCov to see our coverage on iOS swift project.
We’re able to execute our unit tests on Bitrise but when we push the report to CodeCov ignored folders/files are visible and reduce the coverage uselessly.

Codecov Output

gpg: directory '/Users/vagrant/.gnupg' created
gpg: keybox '/Users/vagrant/.gnupg/trustedkeys.gpg' created
gpg: /Users/vagrant/.gnupg/trustdb.gpg: trustdb created
gpg: key 806BB28AED779869: public key "Codecov Uploader (Codecov Uploader Verification Key) <>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpgv: can't allocate lock for '/Users/vagrant/.gnupg/trustedkeys.gpg'
gpgv: Signature made Thu Apr 20 16:45:56 2023 GMT
gpgv:                using RSA key 27034E7FDB850E0BBC2C62FF806BB28AED779869
gpgv: Good signature from "Codecov Uploader (Codecov Uploader Verification Key) <>"
codecov: OK
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   642    0   642    0     0   9023      0 --:--:-- --:--:-- --:--:--  9582
[2023-05-25T14:47:24.368Z] ['info'] 
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/
  Codecov report uploader 0.5.0
[2023-05-25T14:47:24.410Z] ['info'] => Project root located at: /Users/vagrant/git
[2023-05-25T14:47:24.411Z] ['info'] ->  Token found by environment variables
[2023-05-25T14:47:24.438Z] ['info'] Running xcode coversion...
[2023-05-25T14:49:51.210Z] ['info'] Searching for coverage files...
[2023-05-25T14:49:51.643Z] ['info'] Warning: Some files located via search were excluded from upload.
[2023-05-25T14:49:51.643Z] ['info'] If Codecov did not locate your files, please review
[2023-05-25T14:49:51.643Z] ['info'] => Found 1 possible coverage files:
[2023-05-25T14:49:51.643Z] ['info'] Processing /Users/vagrant/git/coverage-report-Test-Staging.json...
[2023-05-25T14:49:51.659Z] ['info'] Using manual override from args.
[2023-05-25T14:49:51.660Z] ['info'] Detected Bitrise CI as the CI provider.
[2023-05-25T14:49:51.673Z] ['info'] Pinging Codecov:*******&branch=feature%2FexcludeGeneratedFilesFromCodeCov&build=320&
[2023-05-25T14:49:51.923Z] ['info']
[2023-05-25T14:49:51.924Z] ['info'] Uploading...
[2023-05-25T14:49:52.137Z] ['info'] {"status":"success","resultURL":""}

and the codecov.yml file :

    - "CoreCommon/CoreCommon/Resources/Strings/Localizable.swift"
    - "**/Resources/**"

Expected Results

I expect the file Localizable.swift to be ignored in the report, and all the files within a “Resources” folder as well.

Actual Results

The file Localizable.swift is still in the code coverage report.

Additional Information

In similar topics, people speaks about the team-bot but I dont understand why it is needed (we do not have a team-bot at the moment).

Thank you,

@Marvin please check the above steps, particularly

I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my codecov.yaml configuration file.

Hello @tom , thank you for your answer.
We use Gitlab, not Github so I thinks it is ok for this part.
And yes I validated my codecov.yaml with the command : curl --data-binary @codecov.yml

@Marvin, got it. I should have read more deeply. You need to set up a team bot. We need it in order to communicate with GitLab to do things like read the yaml file server side or set status checks and add comments. What I suspect is happening is that we aren’t able to read your yaml file from our server because we don’t have the permissioning from a team bot.

@tom , thank you for your quick answer. Indeed, set up a team bot was the solution.
Best regards,

1 Like