-
-
Notifications
You must be signed in to change notification settings - Fork 214
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 Additional Output Formats (ie. JUNIT, SARIF) #805
Comments
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
Not stale :) |
+1 to SARIF support |
@wesley-dean-flexion SPOILER : With v6 (currently in alpha), there will be lots of new linters, often security oriented, and SARIF support managed for the linters that are able to produce it (see |
@nvuillam when is v6 expected to go out? |
@dgutson I have to synchronize with a partner, but for the moment it is planned for mid/end of june :) You are free to use v6 alpha at your own risk, but it's really an alpha version :D |
Is your feature request related to a problem? Please describe.
When using MegaLinter in CI, the output needs to be developer-friendly and easy to reference. Especially if there are a lot of errors that need to be addressed.
Describe the solution you'd like
I would like native support for different output formats, including JUNIT, SARIF, and possibly HTML/PDF.
Describe alternatives you've considered
There are a few issues (Report in JSON and Support for JUNIT artifacts for results visualization) that provide alternative approaches like converting TAP files, but that is not always an option (ie. in self-hosted/shared environments that have limitations and restrictions on what can be installed on the build server).
Additional context
Here are a few tools that provide additional output formats (in case their approach can be easily retrofitted into MegaLinter):
The text was updated successfully, but these errors were encountered: