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

Publish June 18th 2024 archives #358

Closed
23 tasks
github-actions bot opened this issue Jun 18, 2024 · 1 comment
Closed
23 tasks

Publish June 18th 2024 archives #358

github-actions bot opened this issue Jun 18, 2024 · 1 comment
Assignees
Labels
automation Issues relating to automated archiver runs zenodo

Comments

@github-actions
Copy link

Summary of results:

See the job run results [here][1].
[1]: https://github.com/catalyst-cooperative/pudl-archiver/actions/runs/9566582982

Review and publish archives

For each of the following archives, find the run status in the Github archiver run. If validation tests pass, manually review the archive and publish. If no changes detected, delete the draft. If changes are detected, manually review the archive following the guidelines in step 3 of README.md, then publish the new version. Then check the box here to confirm publication status, adding a note on the status (e.g., "v1 published", "no changes detected, draft deleted"):

Tasks

Preview Give feedback

Validation failures

For each run that failed because of validation test failures (seen in the GHA logs), add it to the tasklist. Download the run summary JSON by going into the "Upload run summaries" tab of the GHA run for each dataset, and follow the link. Investigate the validation failure.

If the validation failure is deemed ok after manual review (e.g., Q2 of 2024 data doubles the size of a file that only had Q1 data previously, but the new data looks as expected), go ahead and approve the archive and leave a note explaining your decision in the task list.

If the validation failure is blocking (e.g., file format incorrect, whole dataset changes size by 200%), make an issue to resolve it.

Tasks

Preview Give feedback

Other failures

For each run that failed because of another reason (e.g., underlying data changes, code failures), create an issue describing the failure and take necessary steps to resolve it.

Tasks

Preview Give feedback

Relevant logs

[Link to logs from GHA run][1]

@e-belfer
Copy link
Member

This is a test of auto-creating issues in #357. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Issues relating to automated archiver runs zenodo
Projects
Archived in project
Development

No branches or pull requests

1 participant