-
Notifications
You must be signed in to change notification settings - Fork 1
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
#184: Sbt cross-build is broken #198
Conversation
JaCoCo server module code coverage report - scala 2.13.11
|
a515913
to
c8726d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM so far! We'll need to adjust the required checks on the Repository Settings level as well, because these are not dynamically discovered as the code changes. I can help if you want.
JaCoCo model module code coverage report - scala 2.13.11
|
JaCoCo agent module code coverage report - scala 2.13.11
|
.github/workflows/jacoco_report.yml
Outdated
paths: ${{ github.workspace }}/model/target/jvm-${{ env.scalaShort }}/jacoco/report/jacoco.xml | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
min-coverage-overall: ${{ env.overall }} | ||
min-coverage-changed-file: ${{ env.changed }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
min-coverage-changed-file: ${{ env.changed }} | |
min-coverage-changed-files: ${{ env.changed }} |
I just opened https://github.com/AbsaOSS/atum-service/actions/runs/9227481018/job/25389516611?pr=198 and there is warning:
Warning: Unexpected input(s) 'name', 'min-coverage-changed-file', valid inputs are ['paths', 'token', 'min-coverage-overall', 'min-coverage-changed-files', 'title', 'update-comment', 'skip-if-no-changes', 'pass-emoji', 'fail-emoji', 'continue-on-error', 'debug-mode']
probably also name
should be dropped
.github/workflows/jacoco_report.yml
Outdated
if: steps.jacocorun.outcome == 'success' | ||
id: jacoco-agent | ||
uses: madrapps/jacoco-report@v1.6.1 | ||
with: | ||
name: agent-jacoco-report | ||
paths: ${{ github.workspace }}/agent/target/jvm-${{ env.scalaShort }}/jacoco/report/jacoco.xml | ||
paths: ${{ github.workspace }}/agent/target/spark3-jvm-${{ env.scalaShort }}/jacoco/report/jacoco.xml | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
min-coverage-overall: ${{ env.overall }} | ||
min-coverage-changed-file: ${{ env.changed }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
min-coverage-changed-file: ${{ env.changed }} | |
min-coverage-changed-files: ${{ env.changed }} |
I just opened https://github.com/AbsaOSS/atum-service/actions/runs/9227481018/job/25389516611?pr=198 and there is warning:
Warning: Unexpected input(s) 'name', 'min-coverage-changed-file', valid inputs are ['paths', 'token', 'min-coverage-overall', 'min-coverage-changed-files', 'title', 'update-comment', 'skip-if-no-changes', 'pass-emoji', 'fail-emoji', 'continue-on-error', 'debug-mode']
probably also name
should be dropped
See 6 expected checks, which are visible. It should be removed. |
In README.md:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- pulled
- code review
- local machine test
During the review, I created 2 posts unrelated to the changed files.
.github/workflows/jacoco_report.yml
Outdated
paths: ${{ github.workspace }}/model/target/jvm-${{ env.scalaShort }}/jacoco/report/jacoco.xml | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
min-coverage-overall: ${{ env.overall }} | ||
min-coverage-changed-file: ${{ env.changed }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just like Ladislav said, I think this min-coverage-changed-file
should be changed to min-coverage-changed-files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is not lacking anything, just the suggestions that Ladislav made, then it can be approved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now, I quickly scanned through all the CI logs and it seems good, no warnings left
Closes #184