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

Supports GitHub Actions Attempts #966

Open
srz-zumix opened this issue Sep 8, 2023 · 1 comment
Open

Supports GitHub Actions Attempts #966

srz-zumix opened this issue Sep 8, 2023 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@srz-zumix
Copy link

There is a case where Re-run a job that once failed, it succeeds.
I think the last Attempt is probably being aggregated, but is it possible to aggregate all Attempts?

@Kesin11
Copy link
Owner

Kesin11 commented Sep 9, 2023

@srz-zumix
GitHub provides attempts aware workflow_run and workflow_job API, so it possible to aggregate it.
However I designed GitHub Actions part of CIAnalyzer to not be aware of attempts, it seems not easy to support it.

CIAnalyzer can skip to fetch workflow that was already fetched in previous run, it relies on own metadata JSON file. Currently run_number is used to recognize which build was fetched in the last run, but run_number does not increment when you rerun workflow.
(Try gh api repos/Kesin11/ts-junit2json/actions/runs/6125855885/attempts/1 | jq .run_number and gh api repos/Kesin11/ts-junit2json/actions/runs/6125855885/attempts/2 | jq .run_number).
It should consider new way to skip fetched build in last run.

And I'm also worried about calculating workflow/job duration that uses various time fields (created_at, started_at etc...) correctly when workflow was retried.

I don't have enough motivation to solve this problem at the moment. But if you tackle this issue, I'd be happy to review it.

@Kesin11 Kesin11 added the enhancement New feature or request label Sep 9, 2023
@Kesin11 Kesin11 added the help wanted Extra attention is needed label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants