Add column to summary to include skip reason #4055
Comments
gep13
added a commit
to gep13/cake
that referenced
this issue
Nov 7, 2022
Via a new setting, --Settings_UseSpectreConsoleForConsoleOutput, it is now possible to output the task headers, and task summary using Spectre.Console. This allows for the easy addition of a new column in the task summary, which includes information about _why_ any given task has been skipped. The old CakeReportPrinter is still in play, but some implementation has been moved from within the DefaultExecutionStrategy to the reporter class. Depending on the setting mentioned above, either the Spectre.Console version of the reporter will be added to the IoC container, or the old version will be in place.
gep13
added a commit
to gep13/cake
that referenced
this issue
Nov 7, 2022
Via a new setting, --Settings_UseSpectreConsoleForConsoleOutput, it is now possible to output the task headers, and task summary using Spectre.Console. This allows for the easy addition of a new column in the task summary, which includes information about _why_ any given task has been skipped. The old CakeReportPrinter is still in play, but some implementation has been moved from within the DefaultExecutionStrategy to the reporter class. Depending on the setting mentioned above, either the Spectre.Console version of the reporter will be added to the IoC container, or the old version will be in place.
devlead
pushed a commit
to gep13/cake
that referenced
this issue
Nov 7, 2022
Via a new setting, --Settings_UseSpectreConsoleForConsoleOutput, it is now possible to output the task headers, and task summary using Spectre.Console. This allows for the easy addition of a new column in the task summary, which includes information about _why_ any given task has been skipped. The old CakeReportPrinter is still in play, but some implementation has been moved from within the DefaultExecutionStrategy to the reporter class. Depending on the setting mentioned above, either the Spectre.Console version of the reporter will be added to the IoC container, or the old version will be in place. * fixes cake-build#4055
|
🎉 This issue has been resolved in version v3.0.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
There are times when running a build, when one or more tasks are skipped. Currently, in order to know what caused the task to be skipped, you have to be running in diagnostic mode, and also you have to scroll up through the build output to see the skip reason.
I think it would be useful to include the skip reason for a task in the summary output that is reported at the end of a build.
The text was updated successfully, but these errors were encountered: