-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
[Continuous build] Summary improvment #41
Comments
Thanks for the feedback, Michele. I will take a look, and make some changes. I may not make all of the changes, though - we can discuss. |
The following line is printed by Maven, not SchemaCrawler.
|
sure ;-p |
Please use SchemaCrawler 14.07.04. Follow the instructions on the website, since the configuration and command-line have changed. |
Great news ! Thanks 👍 |
@mbarre : ou have the deb waiting for you for the R&D day tomorrow ;-D |
perfect ! Thanks ;) |
Sharingsome inspiration about the lint summary 👍 https://junit-team.github.io/junit5/#console-runner
|
What's interesting is the left padding to keep comments and datas alignment to make them more readable |
@sualeh We still have some suggestions we have to discuss with Adrien before going back to you. Thanks. |
Glad that it is working for you. On Fri, Mar 18, 2016 at 12:02 AM, Michèle notifications@github.com wrote:
|
Hi Sualeh
It tested the 14.07.03 today, it works nice and the result pretty cool.
So we have some new ideas regarding the summary, here is the result we have now:
Could It be possible to have this :
I have also some others questions :
I was thinking that the summary will be activated for all the linters, but I realized that only linter with
appears in the summary.
Is it possible to have it actived for all linter ? And only put severity level to
critical
and add the<config></config>
if we need the build to fail.If I don't set the loglevel the summary doesn't appears. I have to set loglevel to INFO, but a lot of other logs appears. Is there a loglevel for which only the summary appears ?
Thanks for what you've done, it really rocks :) I am looking forward your responses.
The text was updated successfully, but these errors were encountered: