Add support for circle-ci

[yarikoptic]

e.g. for dandi-api which still uses it.

[jwodder]

@yarikoptic Does dandi-api still use Circle CI? Can I be added to a repository on Circle CI so that I can test out the API?

[yarikoptic]

Actually I don't know if dandi-archive uses circle-ci any longer. Current target is https://github.com/bids-standard/bids-specification/ . Do you need to be "added" to get Read-only access ?

[jwodder]

@yarikoptic I can access at least some part of the API for that project. I'll let you know if anything seems to require being added.

[jwodder]

@yarikoptic It appears I need to be "following" the bids-specification repository (or its pipelines) on Circle CI in order to see anything meaningful, and this apparently requires that I have some sort of access to the bids-standard organization on Circle CI.

[yarikoptic]

are you logged in via github there or have some dedicated different login?

[yarikoptic]

I will request addition of you to bids-standard but may be meanwhile could create some primitive setup for testing https://github.com/con/tinuous-inception to iron support on?

[jwodder]

@yarikoptic I'm logged in via GitHub.

Do you really mean tinuous-inception (in which case I presume it would just fetch logs and do nothing) or tinuous itself?

[yarikoptic]

right -- add circle-ci to tinuous (as we did for travis/appveyor etc) so tinuous-inception could fetch them "as a test".

[jwodder]

@yarikoptic I sent you (I assume) a request to enable Circle CI for the "con" organization.

[jwodder]

@yarikoptic Here's what I've found & figured out about fetching Circle CI logs so far:

• Circle CI has two versions of its API, v1.1 and v2. A notice at the top of the v1.1 docs states "v1 APIs will be deprecated within the next year. We recommend switching to the v2 APIs."
• I cannot find a way to get logs via the v2 API
• This post describes a way to get logs via the v1.1 API, but trying that led me to an S3 URL with an empty response body.
• By inspecting the URLs of the logs links in the web interface, I determined that I can get the logs for a step via the v1.1 API by making a request to /api/v1.1/project/github/:org/:name/:build_num/output/:step/0?file=true. I'm not sure of the meaning of the /0 at the end, but I think it may have to do with parallel runs.

[yarikoptic]

could you post a question on https://discuss.circleci.com/ about v2 API for the logs? would be sad to get support implemented just to see it "gone" within a year.

[jwodder]

@yarikoptic Question posted: https://discuss.circleci.com/t/downloading-build-logs-with-v2-api/44780

[yarikoptic]

so far it seems boils down to use v1.1 API for now

edit: and any possible questions could be cleared up with circleci discuss

[yarikoptic]

there were answers on https://discuss.circleci.com/t/downloading-build-logs-with-v2-api/44780/3 . @jwodder - are they sufficient to get this feature implemented?

[jwodder]

@yarikoptic Those told me nothing I didn't already know. The situation remains the same as before: logs can currently only be downloaded via the v1 API, which is slated for removal.

[yarikoptic]

it seems that only 1 step requires v1 api , the others could be done via v2. So let's get it implemented via v2+v1 mix. It should be trivial to redo one step via v2 whenever time comes.

[yarikoptic]

ping on this @jwodder -- one more project I would have loved to archive logs for is afni, in particular in the wakes of afni/afni#466 and alike so I could see when regressions happened etc.