Skip to content
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

initial waterfall backend #85

Merged
merged 3 commits into from
Sep 5, 2024
Merged

initial waterfall backend #85

merged 3 commits into from
Sep 5, 2024

Conversation

mcmonkey4eva
Copy link
Contributor

adds route /gitcommitsummary to be the backend of the ci-dashboard waterfall

This isn't particularly optimal. at all. but it's a start! towards moving the impl off the frontend and into the backend. Ideally it should precompute this summary data and store in database. For initial impl it just computes on the fly.

Limitation I'm hitting is GetGitcommit seems to supply timestamps properly, but GetGitcommitsummary is giving me 0001-01-01T00:00:00Z which ain't right. I'm not sure why, main difference here is GetGitcommit has a special custom translation layer that does all sorts of special wonk, whereas for GetGitcommitsummary I just let it pass the data through directly, which as far as I can tell should just work? Regardless, commit.Edges.Gitcommit.Timestamp itself appears to be wrong from some debugging, so I'm not sure why that's happening

adds route `/gitcommitsummary` to be the backend of the ci-dashboard waterfall
'timestamp' is empty data
@mcmonkey4eva mcmonkey4eva merged commit 4f92246 into main Sep 5, 2024
5 checks passed
@mcmonkey4eva mcmonkey4eva deleted the initial-waterfall-backend branch September 5, 2024 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant