Description I’m seeing this in multiple repos. Public repository can no longer upload coverage with error: {‘detail’: ErrorDetail(string=‘Unable to locate build via Azure API. Project is likely private, please upload with the Codecov repository upload token to resolve issue.’, code=‘not_found’)} …

Looks like things work as expected with the new uploader. :confetti_ball:

@johlju the bash uploader is being deprecated, would you be able to see if the issue continues with our new uploader

I will test the new uploader as soon as I can. I had to go out of town, but will report back as soon as possible.

We are running into the same issue with the new uploader. Here is an example log: https://dev.azure.com/mdolab/Public/_build/results?buildId=2315&view=logs&j=008c1c60-593d-5c43-72f9-a33900ae6572&t=762b036c-c79c-5303-ecee-99e8dd294175

I am also experiencing this issue. Originally I thought this was due to the fact that we were using the deprecated bash uploader, so I moved to using the new uploader and am getting the exact same error. This seems like a problem with the API, not with the client application. I opened an issue with…

Today two repos uploaded the code coverage again. @tom was it a change on your side?

@johlju yes, we made a change on Friday that fixed an issue with Azure. Are you still seeing an issue? cc: @sseraj @samdoran

Yesterday two repos uploaded correctly again using the bash uploader. I have not verified that the new uploader works since I haven’t yet have time to switched uploader in a repo. Assuming other people will confirm that the new uploader works too. For me I’m happy to close this.

Unfortunately, we are now seeing a different error: [2021-10-11T16:05:28.238Z] ['error'] Error POSTing to https://codecov.io: 500 {"error": "Server Error (500)"} [2021-10-11T16:05:28.238Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: Internal Serv…

Our nightly builds that upload coverage reports using the bash uploader started working again after the server side change made on Friday. I am still doing some testing with the new uploader. I, too, saw that 500 error on Friday when I was testing.

Currently the bash uploader is working properly, but it appears like the new uploader only works from Azure Pipelines if a token is supplied. If no token is supplied, I see a 500 error with the new uploader. I’m trying with a token with the new uploader to see if that works.

Public repositories can no longer upload coverage with error "Unable to locate build via Azure API."

Support Bug Fixes

samdoran October 15, 2021, 4:58pm 16

Looks like things work as expected with the new uploader.

New uploader doesn't find the repository without token; stalls under Windows

Topic		Replies	Views
CodeCov Uploads from Azure Pipelines are failing with 'Build numbers do not match' Bug Fixes	43	2685	January 5, 2021
New uploader doesn't find the repository without token; stalls under Windows Support	11	674	October 27, 2021
Changed name for private repo and it no longer uploads Support cpp	3	420	February 23, 2021
Generic error uploading Coverage reports Support	6	308	July 22, 2021
Buildkite Codecov Support	1	187	January 4, 2023

Public repositories can no longer upload coverage with error "Unable to locate build via Azure API."

Related topics