You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dotnet tool install step returns a non-zero exit code if the tool is already installed, so it fails on repeated runs or if run after dotnet tool install already installed nbgv.
We should make this more resilient.
Also, we should consider not installing the tool globally. This is useful if the agent the action runs on is shared or reused across runs. Is that possible? In Azure Pipelines there are "private agents" which make it important for tasks to not change machine-wide state. Is such the case here?
The text was updated successfully, but these errors were encountered:
The
dotnet tool install
step returns a non-zero exit code if the tool is already installed, so it fails on repeated runs or if run afterdotnet tool install
already installed nbgv.We should make this more resilient.
Also, we should consider not installing the tool globally. This is useful if the agent the action runs on is shared or reused across runs. Is that possible? In Azure Pipelines there are "private agents" which make it important for tasks to not change machine-wide state. Is such the case here?
The text was updated successfully, but these errors were encountered: