Microsoft.Build.Traversal SDK doesn't traverse the project tree with PublishContainer target

[oats4goats]

Hey!

I'm now exploring the PublishContainer target for my CI pipeline (sdk-container-builds). I have a tree of projects and I can build the containers by running dotnet cli from inside the leafs without use of traversal sdk.

However when I use a .proj file in the root of my tree (generated by dotnet-affected tooling) to build and publish all the affected projects in my tree, the job doesn't even start.

It seems to be checking Publishable and EnableSdkContainerSupport props in the said .proj file, which are false by default, and then skips publishing the containers altogether without traversing the tree and reaching the leafs with the properly configured props in .csproj files.

Is it an intended behavior?

Thanks for looking into this!

--
Mitya

[artiomchi]

I'm running into the same issue, and I'm not sure if this was fixed or not? I've also got a generated .proj file using the dotnet-affected tool, which is a traversal project.

To publish my projects, I use the following command:

dotnet publish .\affected.proj -c Release /t:PublishContainer

The command will run the build and publish steps to generate the project outputs in the publish folder, but it never runs the PublishContainer task to actually generate the docker containers.

I've got the latest versions of the .NET SDK installed (to date): 8.0.410 and 9.0.300.

Was that supposed to have been solved by the linked PR? Am I missing something? Or was that solved, but will only be available in a future build?

Pinging Matt Kotsenas (@MattKotsenas) and Andy Gerlicher (@AndyGerlicher) since you were involved above :)

[MattKotsenas]

I've been using it successfully. You do need to update your Traversal SDK to 4.1.82, which might be at the top of your dirs.proj file, or may be in your global.json file.

Could it be that you're running an older version?

If not, I'd suggest filing a new issue with a repro case.

[artiomchi]

That did it! I thought it was part of the SDK, and didn't realise it's coming from NuGet. dotnet-affected does indeed generate use version 4.1.0 which is the last version before this patch was applied. Thank you!