Fix/fetch executor information #8
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature/steps stream
Feature/key properties
…time-buffer-thing Amann/feature/no more hacky time buffer thing
…at at the end anyways
…okmarks Amann/feature/incremental bookmarks
…-on-failed-gets Debug: Get more information on failed gets
Fix/aged out pipelines
…y of these workflows
…gging-information Feature: More debugging information
…-cancelling-old-pipelines Feature/tools for bulk cancelling old pipelines
…is_completed-90-days-old Fix: CircleCI does not allow the state of aged out pipelines to change
* Add gitleaks scan to CI * update secops orb
…or-data Feature: Pull available useful fields from jobs api
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Presently, the data that this tap for jobs focuses solely those data objects returned by fetching all of a workflow's jobs: https://circleci.com/docs/api/v2/index.html#operation/listWorkflowJobs
Those objects, are distinctly different from the full Job Details: https://circleci.com/docs/api/v2/index.html#operation/getJobDetails
This tap is still leveraging the V1 Build implementation to be able to fetch step information: https://circleci.com/docs/api/v1/index.html#jobs
Unfortunately, neither the slimmed down Workflows Jobs data, nor the V1 Build information, has details about things like parallelism, contexts, nor executor (which is the real data I personally am after). So, instead, we submit yet another request to fetch the V2 job details.