dotnet publish: AfterTargets="AfterPublish" triggers before publish is complete

[catmanjan]

Hello we have a project like many others publishing docker images to kubernetes.

To try to make developers life easier I added the following to my pubxml:

<?xml version="1.0" encoding="utf-8"?>
<!--
https://go.microsoft.com/fwlink/?LinkID=208121.
-->
<Project>
  <PropertyGroup>
    ...snip...
  <Target Name="CustomActionsBeforePublish" BeforeTargets="BeforePublish">
    <Exec Command="az acr login -n icognitionhydra" />
  </Target>
  <Target Name="RestartPod" AfterTargets="AfterPublish">
	<Exec Command="az aks get-credentials -g hydraKubernetes -n hydra" />
    <Exec Command="kubectl rollout restart deployment hydra" />
  </Target>
</Project>

However, I notice the RestartPods target occurs before the image is fully published to my ACR, resulting in a race condition that sometimes Kubernetes beats, meaning the old image is deployed instead of the new...

What should my AfterTargets be set to if I want it to only run the rollout commands after the container is fully published to ACR?

[baronfel]

I'd need to take a look at a binlog to double-check, but my first recommendation would be the PublishContainer target - that's the target that actually creates + pushes container images to the desired destination, whether that's local daemon, tarball, or remote registry.

[catmanjan]

@baronfel Thanks I'll try that now - out of interest where can someone read about all the different "AfterTargets" options?

I promise I did try searching myself!

[catmanjan]

@baronfel I just tried this, but the commands never executed

  <Target Name="RestartPod" AfterTargets="PublishContainer">
	<Exec Command="az aks get-credentials -g hydraKubernetes -n hydra" />
    <Exec Command="kubectl rollout restart deployment hydra" />
  </Target>

[baronfel]

Is there any way you can get an https://aka.ms/binlog and use the viewer to take a look? I added a target just like yours to a sample project I had, and then published that project with dotnet publish -t:PublishContainer and see the target firing as I expect: