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

Add a comment once e2e finishes #5308

Open
zroubalik opened this issue Dec 21, 2023 · 13 comments
Open

Add a comment once e2e finishes #5308

zroubalik opened this issue Dec 21, 2023 · 13 comments
Labels
feature-request All issues for new features that have not been committed to help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing

Comments

@zroubalik
Copy link
Member

zroubalik commented Dec 21, 2023

Proposal

In order to be able to tell which e2e test run has passed, we should generate a new comment instead of just adding an emoji to the original comment (the one with /run-e2e command). The new comment should quote the original comment so we have a reference.

The benefit is, that we get a notification that e2e test run has finished, so we can check the results.

Old Proposal (we don't want to go this direction)

In order to be able to tell which PR is ready for final review/merge, it would be nice if a label (eg e2e-passed) could be added to the PR.

If the there are additional commits/pushes to the PR, the label should be automatically removed.

@zroubalik zroubalik added feature-request All issues for new features that have not been committed to testing labels Dec 21, 2023
@JorTurFer
Copy link
Member

Isn't it enough just the CI check?

@zroubalik
Copy link
Member Author

zroubalik commented Dec 21, 2023

Maybe 🤔

I am thinking how to do a review properly, once I trigger e2e test on a couple of PRs, I want to get back to these once they finish.

Most likely we can disregard this idea.

@JorTurFer
Copy link
Member

JorTurFer commented Dec 21, 2023

Currently we can see if e2e has passed (or being skipped) here:
image

Red cross or orange circle means failures or in-progress checks
But we can try with the labels

@zroubalik
Copy link
Member Author

Yeah I know, maybe this is more about me, knowing when a new e2e test execution finished, so I can review the result. Sometimes it is hard to keep track. I should probably solve this on my side, the label is an overkill.

@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Dec 21, 2023
@zroubalik
Copy link
Member Author

@JorTurFer what would actually help is to get some kind of notification once the e2e run finishes. Now it just updates a comment which is not something that generates notifications.

@JorTurFer
Copy link
Member

Actually, the notification is sent on every comment

@JorTurFer
Copy link
Member

We could try to notify somehow to a slack channel. Could it help? If yes, we have to request the slack channel in kubernetes workspace

@zroubalik
Copy link
Member Author

Actually, the notification is sent on every comment

It is not sent on comments updates, or am I mistaken? I am interested in getting a notification once e2e test run finishes.

Slack notification is probably an overkill.

@tomkerkhove
Copy link
Member

Actually, the notification is sent on every comment

It is not sent on comments updates, or am I mistaken? I am interested in getting a notification once e2e test run finishes.

Slack notification is probably an overkill.

I can see value in a comment post or so indeed

@zroubalik zroubalik changed the title Add a label to PR once the e2e passes Add a comment once e2e finishes Jan 2, 2024
@zroubalik
Copy link
Member Author

Modified the proposal to create a new comment, instead of just a label.

@zroubalik zroubalik reopened this Jan 2, 2024
@github-project-automation github-project-automation bot moved this from Ready To Ship to Proposed in Roadmap - KEDA Core Jan 2, 2024
@tomkerkhove
Copy link
Member

I think we should use the same for starting e2e tests instead of updating the message with test run link given that does not trigger GitHub notification, but it might be just me.

@zroubalik
Copy link
Member Author

The comment should mention whether the e2e passed or not, if not, it should also print the failed tests.

Copy link

stale bot commented Mar 16, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Mar 16, 2024
@tomkerkhove tomkerkhove added the help wanted Looking for support from community label Mar 18, 2024
@zroubalik zroubalik added stale-bot-ignore All issues that should not be automatically closed by our stale bot and removed stale All issues that are marked as stale due to inactivity labels Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing
Projects
Status: Proposed
Development

No branches or pull requests

3 participants