Closed sfwester closed 2 months ago
I see this related entry in the changelog
Fixed invoked targets to not be excluded from skipping
Which looks like it was brought in by the fix for #1414.
But I don't think the behaviour I observed is intended? Otherwise, it is not clear if the empty --skip option can provide any value.
I initially thought the issue was related to the Nuke.Global .NET tool, but after investigating further, I discovered that the problem was with the version of Nuke.Common in my build.csproj file.
To resolve this, I had to downgrade the Nuke.Common NuGet package to version 8.0.0. Once I made that change, everything worked as expected.
I’m just leaving this comment here for any newbies like me who might run into the same problem!
Usage Information
8.1.0 / 8.0.300 / net8.0 / Windows 11
Description
When I upgraded to 8.1.0 I observed that the
--skip
option, with no arguments, has started skipping the provided target.Reproduction Steps
From an empty directory
Expected Behavior
The Compile target is not skipped.
Note these results are observed if the
Nuke.Common
dependency is knocked down to 8.0.0 in the_build.csproj
Actual Behavior
The
Compile
target is skipped.Regression?
Yes, it works as expected in 8.0.0.
Known Workarounds
Skip all the the dependencies explicitly. e.g.,
Could you help with a pull-request?
No