Writing summaries to file via option#344
Merged
Merged
Conversation
# Conflicts: # builds/pint
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While using Pint in CI pipelines and Gitlab interface is neat feature*, fact that you have to dump it into file that's not quite human readable (and therefore cannot be read from CI pipeline logs and on non-Ultimate Gitlab instances), is a bit less so
Following PR adds ability to write summaries to a file, potentially in a different format from one used to write the summary to CLI
For example:
Outputs result of a scan in Pint's default elaborate printer, while also writing to a file using GitlabReporter
New options are:
--output-to-file=- additionally write summary into this file. Using this option requires specifying either--output-formator--format--output-format=- accepts same values as--format, and if not defined, falls back to--format. If neither is defined, file isn't written into* In theory, it's Gitlab Ultimate feature. We over here using Community version, which does not quite display Code Quality reports in Gitlab interface