-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CODE-842] Uploader fails from public project in Azure Pipelines without token #421
Comments
Setting the slug still resulted in failure. Maybe the issue is something with the Codecov API not parsing the build URL correctly? Just a wild guess based on the error, which seems like it is coming from the API and not from the client. |
Looking into this further, it appears the Same failure from the bash uploader
|
Hi @samdoran , Is your Azure instance private? We can't access the API needed for tokenless in that case, which is usually why we say you need a token. |
Nope, it's public |
Looks like we have a bug in the login that detects if the response to thhe API call is JSON or not. Investigating. |
@samdoran Can you test if this is still an issue? It should be fixed now. |
Sure thing! |
My simple test repo succeeds now. I will kick off a run on our main repo (that takes ~45 minutes). |
I'm seeing a different error now on our main repo: Failed job output
|
Goodie. Let me see what the server says. |
@samdoran Does it still work with a token? |
It's been a Monday 😖. I'm just now getting to testing this. I'll report back with what I find. |
Uploads using the |
Uploading using the new uploader with the token does work. I would rather not have to specify the token for the new uploader, though. |
I just tested again (because why not 😁) and I get a 500 error with the new uploader if the token is not supplied.
|
@samdoran It looks like Azure tokenless possibly never worked. Can you test if it works with tokenless if you pass a |
Azure Pipelines currently works tokenless using the Successful upload using the bash uploader with no token
I will test the new uploader providing a slug and no token. Thank you for all your help! |
Ah, bash is sending the slug., uploader is not. @mitchell-codecov |
Confirmed that specifying the slug works. I'll open a PR that sets the slug for AZP. |
Describe the bug
When running the uploader from Azure Pipelines on a public project, the uploader fails to upload reports unless the token is set.
To Reproduce
Steps to reproduce the behavior:
coverage -f [file] -n [name]
from a public project in Azure Pipelines with no token specifiedExpected behavior
The coverage report is uploaded successfully.
Actual behavior
The provider is correctly detected but upload of coverage files fails.
Failed job output
Additional context
The
bash
uploader worked without specifying a token but the new uploader does not.I am currently experimenting to see if setting just the slug, not the token, is sufficient. It looks curious that the slug is blank (exploded for legibility):
The text was updated successfully, but these errors were encountered: