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

Run the PR test after merge and report to channel if it fails #5962

Merged
merged 4 commits into from
May 9, 2022

Conversation

michaelkaye
Copy link
Contributor

Additionally move sonarqube as the only nightly run; and again report to the channel only if it fails.

This should reduce noise in the channel and also provide feedback on who merged a PR with a failing test in it.

@michaelkaye michaelkaye requested review from a team, yostyle and mnaturel and removed request for a team May 6, 2022 14:36
@github-actions
Copy link

github-actions bot commented May 6, 2022

Unit Test Results

122 files  ±0  122 suites  ±0   2m 28s ⏱️ +15s
205 tests ±0  205 ✔️ ±0  0 💤 ±0  0 ±0 
690 runs  ±0  690 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 5cc0b86. ± Comparison against base commit 0b00f97.

♻️ This comment has been updated with latest results.

needs:
- sonarqube
- codecov-units
if: always() && needs.sonarqube.result != "success" and needs.codecov-units.result != "success"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this condition, I would have expect something like:

if: always() && (needs.sonarqube.result != "success" || needs.codecov-units.result != "success")

I guess we should notify in case either the sonarqube job or the code coverage job fails. And also I am not sure we can use and instead of &&? What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Argh, yes; I made this fix in post-pr.yml but not here - good catch.

@michaelkaye michaelkaye requested a review from mnaturel May 9, 2022 10:21
Copy link
Contributor

@mnaturel mnaturel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but I see there are some conflicts to be resolved.

@michaelkaye michaelkaye force-pushed the michaelk/run_pr_test_after_merge branch from 4ea18d4 to 5cc0b86 Compare May 9, 2022 13:09
@michaelkaye michaelkaye enabled auto-merge (squash) May 9, 2022 13:10
@michaelkaye michaelkaye merged commit 39c2b08 into develop May 9, 2022
@michaelkaye michaelkaye deleted the michaelk/run_pr_test_after_merge branch May 9, 2022 13:49
ouchadam pushed a commit that referenced this pull request May 12, 2022
* Fork sonarqube run into a nightly build, report failures back to channel.
* Each PR triggers a build after merge, report failures back to channel.
piersonleo pushed a commit to piersonleo/element-android that referenced this pull request Jun 7, 2022
…t-hq#5962)

* Fork sonarqube run into a nightly build, report failures back to channel.
* Each PR triggers a build after merge, report failures back to channel.
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.

2 participants