Skip to content

CakeReportPrinter should be disabled in Verbosity = QuietΒ #2101

Closed

Description

@Gargony

I expect no extra lines from cake-build in Verbosity Quiet mode.

Activity

  1. patriksvensson commented on Mar 26, 2018

    @patriksvensson
    Member

    @Gargony I would disagree. Setting the verbosity to quiet, simply tells the logger to only output warnings and errors. The report however I think is something that you usually want to see when a build finished even if you want to remove clutter from the log.

    We could however introduce a --no-report argument to Cake, to tell Cake not to show this.

  2. Gargony commented on Mar 27, 2018

    @Gargony
    Author

    Thank you for your proposal.
    Ok, argument approach also cover my expectations. But in my practices with other command line tools, verbosity applied to all output information (e.g. MSBuild).

  3. tapika commented on Mar 28, 2023

    @tapika

    Any progress on this one ?

  4. augustoproiete commented on Mar 28, 2023

    @augustoproiete
    Member

    @tapika No one working on this one at the moment. PR would be welcome

  5. deniszykov commented on Apr 14, 2023

    @deniszykov

    This is kinda bug, not a "feature request".

    Unswitchable printing into stdout and cluttering the output is undesired behavior.

  6. augustoproiete commented on Apr 14, 2023

    @augustoproiete
    Member

    @deniszykov Are you sending a PR for this one?

  7. augustoproiete commented on Apr 14, 2023

    @augustoproiete
    Member

    Possible workaround in the meantime:

    dotnet cake >/dev/null 2>&1
    

    Should suppress all output.

  8. deniszykov commented on Apr 14, 2023

    @deniszykov

    Sure why not, but it will be straight and simple - verbosity Quiet = no logging output.

    dotnet cake >/dev/null 2>&1

    Also suppress desired output.

  9. added 3 commits that reference this issue on Dec 6, 2025
  10. added this to the v6.2.0 milestone on Mar 3, 2026
  11. added a commit that references this issue on Mar 3, 2026
  12. github-actions commented on May 22, 2026

    @github-actions

    πŸŽ‰ This issue has been resolved in version v6.2.0 πŸŽ‰

    The release is available on:

    Your GitReleaseManager bot πŸ“¦πŸš€

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions