circleci-queue
circleci-queue copied to clipboard
eddiewebb
BLOCKED - Change to Circle CI V2 APIs
Is your feature request related to a problem? Please describe.
We are currently seeing stale data returned from CircleCI on the v1.1 endpoints for running jobs. CircleCI has said that we should migrate off of those APIs. Unfortunatley, there isn't a clear 2.0 API paradigm to switch over to, so we need to determine what the best set of APIs to use is (and we will end up making more calls).
Describe the solution you'd like
Remove dependencies on the deprecated V1.1 CircleCI API.
Additional context CircleCI has said they have a filed an internal incident for the V1.1 data issue, but I don't think we can rely on a fix there.
Ah, I found this project today after running into issues with seemingly stale data from the v1 API using bellkev/circle-lock-test, which had been working fine for us until yesterday. Perhaps there's a more widespread issue with their v1/1.1 APIs. Still, I'd love if this could be using v2 exclusively!
@mikebranski, I have been speaking with CCI about the issues on the staleness and they are tracking a fix internally. It's unclear to me how committed they are to doing it since they are pushing us to adopt the V2 APIs. I think we will need to get a list of all pipelines, and then iterate and query to determine the status of each one to determine if one falls into the "blocking/running" paradigm.
@promiseofcake I've been speaking with CCI support and received some interesting information. Specifically, they still use v1/1.1 internally, so hopefully things smooth out and migrate to v2 eventually.
Message from CCI:
Thanks for thinking about changing to eddiewebb's orb and sharing the issue with API staleness. It does help when there are many users reporting similar issue for product team to take more consideration. Currently the v1/1.1 is also used internally as well and we would release the v2 version of equivalent API and then deprecate the API. I'm sorry but currently we do not have the equivalent API on v2.
Thanks for that @mikebranski. For what it's worth I took the work here and made one work with the V2 APIs, copied w/ attributed in my username. I wanted to take advantage of the new Orb publishing flow and was easier to start over.