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

Support Additional Output Formats (ie. JUNIT, SARIF) #805

Closed
AErmie opened this issue Oct 4, 2021 · 6 comments
Closed

Support Additional Output Formats (ie. JUNIT, SARIF) #805

AErmie opened this issue Oct 4, 2021 · 6 comments
Labels
enhancement New feature or request

Comments

@AErmie
Copy link

AErmie commented Oct 4, 2021

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):

@AErmie AErmie added the enhancement New feature or request label Oct 4, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2021

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

@github-actions github-actions bot added the O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity label Nov 4, 2021
@nvuillam
Copy link
Member

nvuillam commented Nov 18, 2021

Not stale :)
It will require a lot of work, probably be in v6, but should happen someday (probably with SARIF format) and bring MegaLinter to the next level ;)

@nvuillam nvuillam removed the O: stale 🤖 This issue or pull request is stale, it will be closed if there is no activity label Nov 18, 2021
@wesley-dean-flexion
Copy link
Contributor

+1 to SARIF support

@nvuillam
Copy link
Member

nvuillam commented Mar 10, 2022

@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 icons ) , and a single MegaLinter SARIF result that will be the aggregation of all linter SARIF outputs :)

https://megalinter.github.io/v6-alpha/supported-linters/

@dgutson
Copy link

dgutson commented May 30, 2022

@nvuillam when is v6 expected to go out?

@nvuillam
Copy link
Member

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants