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

Generate job annotations without GHA REST API #23445

Merged
merged 1 commit into from
Sep 17, 2024

Conversation

nineinchnick
Copy link
Member

Description

The separate annotate workflow was added to work around permission issues in forked repositories. This is not needed when not using the GHA REST API.

Adding annotations via the API was not working correctly anyway, since it added a check for a commit, but one commit can have multiple runs associated with it, and the check sometimes did not show up in the main run.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@cla-bot cla-bot bot added the cla-signed label Sep 16, 2024
@nineinchnick
Copy link
Member Author

This is a draft, because trinodb/github-actions#34 and starburstdata/action-testng-report#8 are not merged yet.

@nineinchnick
Copy link
Member Author

Tested in https://github.com/nineinchnick/trino/actions/runs/10884950374?pr=18

The annotations now show up in the run summary view even before the run finishes, which is very nice, since we have so many long running jobs.

@nineinchnick nineinchnick changed the title [WIP] Generate job annotations without GHA REST API [Generate job annotations without GHA REST API Sep 17, 2024
@nineinchnick nineinchnick changed the title [Generate job annotations without GHA REST API Generate job annotations without GHA REST API Sep 17, 2024
@nineinchnick nineinchnick marked this pull request as ready for review September 17, 2024 12:48
@nineinchnick
Copy link
Member Author

There's a potentially flaky test failure in sqlserver and we can already see this working as expected:
image

@wendigo
Copy link
Contributor

wendigo commented Sep 17, 2024

@nineinchnick nice

@wendigo
Copy link
Contributor

wendigo commented Sep 17, 2024

@nineinchnick can we upgrade the node versions to reduce the warnings?

The separate annotate workflow was added to work around permission
issues in forked repositories. This is not needed when not using the GHA
REST API.

Adding annotations via the API was not working correctly
anyway, since it added a check for a commit, but one commit can have
multiple runs associated with it, and the check sometimes did not show
up in the main run.
@wendigo wendigo merged commit 423a46f into trinodb:master Sep 17, 2024
95 checks passed
@github-actions github-actions bot added this to the 458 milestone Sep 17, 2024
@nineinchnick nineinchnick deleted the annotate-runs branch September 18, 2024 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants