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 a consolidated JaCoCo report from multiple subprojects and split test jobs #3147

Merged
merged 3 commits into from
Feb 13, 2025

Conversation

MMcM
Copy link
Collaborator

@MMcM MMcM commented Feb 13, 2025

  • Stop creating per-subproject JaCoCo reports.
  • Add a new top-level Gradle task to take the outputs of build / test and generate a single report.
  • Publish .exec files out of both -test jobs.
  • Add a fourth pull-request workflow job that downloads those artifacts and generates a report.
  • Adjust the separate workflow_run workflow (needed to get pull_request commenting access) to use that report.

MMcM added 3 commits February 12, 2025 16:52
Add another top-level report task to combine them.
* `pull_request` test jobs also publish JaCoCo `.exec` artifacts.
* `pull_request_coverage` runs in head branch and generated combined JaCoCo report from those.
* `pull_request_comment` runs in target branch and adds comment form that.
@MMcM MMcM requested a review from alecgrieser February 13, 2025 16:20
Comment on lines +40 to +57
- name: Checkout sources
uses: actions/checkout@v4.2.2
- name: Setup Base Environment
uses: ./actions/setup-base-env
- name: Setup FDB
uses: ./actions/setup-fdb
- name: Run Gradle Test
uses: ./actions/gradle-test
with:
gradle_command: :fdb-record-layer-core:test :fdb-record-layer-core:destructiveTest
gradle_args: -PreleaseBuild=false -PpublishBuild=false
- name: Publish Test Reports
if: always()
uses: actions/upload-artifact@v4.6.0
with:
name: core-test-reports
path: |
test-reports/fdb-record-layer-core/
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Adjusting indentation to match the rest of the file.

@alecgrieser alecgrieser merged commit 1df5e2e into FoundationDB:main Feb 13, 2025
4 checks passed
Copy link

Overall Project 80.2% 🍏

There is no coverage information present for the Files changed

Copy link

Overall Project 80.17% 🍏

There is no coverage information present for the Files changed

@MMcM MMcM deleted the coverage-workflows branch February 13, 2025 18:28
Copy link

Overall Project 80.19% 🍏

There is no coverage information present for the Files changed

alecgrieser added a commit to alecgrieser/fdb-record-layer that referenced this pull request Feb 13, 2025
I noticed that all of the comments are being sent to FoundationDB#3147, the change which introduced `pull_request_comments.yml`, which I think is a mistake. To avoid that,
this tries to use a job within the PR
alecgrieser added a commit to alecgrieser/fdb-record-layer that referenced this pull request Feb 13, 2025
I noticed that all of the comments are being sent to FoundationDB#3147, the change which introduced `pull_request_comments.yml`, which I think is a mistake. To avoid that,
this tries to use a job within the PR
Copy link

Overall Project 80.19% 🍏

There is no coverage information present for the Files changed

1 similar comment
Copy link

Overall Project 80.19% 🍏

There is no coverage information present for the Files changed

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