-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support glob format for xml files #96
Comments
@ty1824 Thanks for bringing this up! I will look into making the action compatible with multi-module projects |
Thanks for providing this action and the quick response 😊 |
Realized I never left an example. My pull request build action: https://github.com/ty1824/dialector/blob/main/.github/workflows/pull-request-build.yml |
@ty1824 With v1.7 support for multi-module project got introduced. Basically you can pass now multiple report files to the action like this: ...
uses: mi-kas/kover-report@v1
with:
path: |
${{ github.workspace }}/project1/build/reports/kover/report.xml
${{ github.workspace }}/project2/build/reports/kover/report.xml Does this resolve your problem? |
@mi-kas Is it possible to use dynamic path like '**/reports/kover/report.xml', since we are calling this in reusable action created for multi module kotlin projects. I tried release v1.7 still it throws "Error: ENOENT: no such file or directory" for below dynamic path
|
@dubakur Currently only exact paths are supported as we read files in via Line 14 in aedeaa4
But at first glance dynamic paths should also possible by using a library like |
Any update here? We have a big mono repo with a lot of modules and its hard to pre know all report files |
I have a multi-module project and would like to publish each individual coverage report without having to manually specify the file. However, if I use a glob format, I get the error:
Error: ENOENT: no such file or directory, open '**/reports/kover/report.xml'
Ideally this would work similarly to other test reporting actions (I am currently using dorny/test-reporter@v1, for example).
I realize I could use a merged report, but I was hoping to avoid that in this case.
The text was updated successfully, but these errors were encountered: