-
Notifications
You must be signed in to change notification settings - Fork 176
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
[Enhancement] Output reports in a standard format #265
Comments
Thanks for bringing this up @benbridts Curious, any votes on which option will support your use case best? JUnit? Cucumber JSON? etc? |
I'm happy to open another issue for this, but I came here with the same ask specifically around getting some kind of output from the |
For my use case any output that is supported by CodeBuild would be great |
Thank you @benbridts Will take this back to the team. @drmmarsunited Noted. |
+1 on this one. Any test report format supported by CodeBuild would be great. |
Related: Add support for SARIF [Enhancement] #412 |
Hi @benbridts, @drmmarsunited and @fabiodouek just wanted to let the 3 of you know that we now have support for JSON/YAML/JUnit reporters for both test and validate command I am going to go ahead and close out this issue. Feel free to reopen if necessary |
Is your feature request related to a problem? Please describe.
When using Guard as part of a CI/CD pipeline, I would like to use my current reporting tool to track rule failures and success over time and use my tools integrations (ie links to files and lines) to easily navigate through source code
Describe the solution you'd like
There are multiple popular report file outputs (CodeBuild supports 6 different ones), picking one or two from that list and adding a
--report
option would be great.Additional context
I don't think this should replace the current output formats (I might want single-line output for my build log in addition to the report). A
--output none
option might be useful, but> /dev/null
would work in a lot of environments too.The text was updated successfully, but these errors were encountered: