Add support of uploading from Cirrus CI without token

Summary

Add support of uploading from Cirrus CI without token

Description

I see “Repository Upload Token” and:

Note: Token not required for public repositories uploading from Travis, CircleCI or AppVeyor.

Please, add Cirrus CI to this list.

Examples

image

Versions

Current website version.

1 Like

Hi @AlexWayfer

We are able to do this for the other CI providers because we can use their API to confirm the upload is happening as part of a running job.

As far as I know, Cirrus CI doesn’t have an API that allows us to do this, so this feature is not possible or planned. If this changes, we will be happy to take another look and prioritize.

Hi. Did you see https://cirrus-ci.org/api/ ? Just the first link in Google search, but I’m not sure that this is suitable for your usage.

Not sure. Checking with the engineer who generally handles the tokenless code :slight_smile:

Hi, two weeks passed, what is progress?

Hi @AlexWayfer!

Ib here from Codecov - thanks for your question. From a preliminary analysis, the cirrus api seems to be returning the proper information needed to support tokenless. The only thing I’d be concerned about is rate limiting - I can’t seem to find any information about that on their website.

In terms of an implementation timeline, I’m not sure if we’ll be able to get to this right away, but I will definitely put in a ticket for this on our backlog

Best,
Ib

Thank you!

Here is Cirrus CI member, you can contact with him about rate limits or other questions: https://github.com/fkorotkov

There are rate limits on mutations via the API but there are no limits at the moment on reads and I believe you only need to read from the API. I’m willing to help in any way to adopt tokenless uploads from Cirrus. Please let me know how can I help. Here is my email: fedor@cirruslabs.org.

1 Like

Hey all, just updating that this feature is in our backlog and we will prioritize depending on interest from our general community. Thanks!

Jerrod

Hi all, thanks again for your patience here. We’ll look into getting this supported in the next few weeks.

1 Like

Excuse me, but how many “few” weeks? One month (4 weeks) have already passed.

Hi @AlexWayfer apologies on the delay here. This is very much on my roadmap, but we are currently in the process of refactoring key parts of this system. In order to prevent double work, we are waiting for that to be completed first.

2 Likes

OK, thank you, will wait.

Hi @AlexWayfer, just an update here. We have finished development here but are still refactoring other pieces of our system. However, this should make it to the next major update. I’ll update here when that happens.

@AlexWayfer, we rolled out some changes for Cirrus CI tokenless. Would you be able to test it out and see if it’s working as you expect?

Doesn’t seem working: Cirrus CI

Got it, thanks @AlexWayfer. I’ll see what went wrong and let you know when we’ve addressed it.

The error has been changed (from 400 to uknown repo) on re-run: Cirrus CI

@AlexWayfer, apologies I was dealing with COVID the last few weeks. Do you have a more recent run of the Could not determine repo and owner?

I am also interested in this feature.

@tom I do not know if I can help here but here are some fresh attempt to upload coverage report from Cirrus CI : Cirrus CI