(#302 #306) Update to Cake 6.0.0 and add GitHub Report Printer#307
(#302 #306) Update to Cake 6.0.0 and add GitHub Report Printer#307nils-a merged 4 commits intocake-contrib:developfrom
Conversation
|
@nils-a this is currently failing the build due to this: 
Does this need an update to the |
|
You can see an example output from these changes here: https://github.com/gep13/cake-test/actions/runs/19597731877 
|
|
I have been meaning to create this PR for a while, but it felt like now was the time, since now we have this ability to always have a task summary, even when the build fails. This means, that we can always write this information in the Step Summary in GitHub Actions. This is what I am trying to show in the image above, since the Windows build failed, but the Step Summary was still updated. |
nils-a
left a comment
There was a problem hiding this comment.
The modules need to stay at net8.0 - this is the minimal TFM supported by Cake 6.
Yes, that too. 😁 CakeContrib.Guidelines 1.7.0 added support for Cake v6. |
Bump all the Cake.* references, and also switch to using .NET 10.
This will be used to improve the Cake output when running on GitHub Actions. This includes the task summary being written out to the Step Summary. With the latest releases of Cake, the task summary is written out even when there is a failed build, so this means that we can capture that output into the Step Summary, to get an overview of which task might have failed the build.
Update the default output, as well as the Azure Pipelines output, to include information about the status of the task, and all the skip reason, if there is something. This change brings consistency to the output after the addition of the new GitHub Actions Report Printer.
3cd7a9c to
8e0b355
Compare
|
@nils-a this is ready for another review. Latest GitHub Actions run is here: https://github.com/gep13/cake-test/actions/runs/19612025024 |
Bump all the Cake.* references, and also switch to using .NET 10.
The GitHub Report Printer will be used to improve the Cake output
when running on GitHub Actions. This includes the task summary
being written out to the Step Summary.
With the latest releases of Cake, the task summary is written out even
when there is a failed build, so this means that we can capture that
output into the Step Summary, to get an overview of which task might
have failed the build.