search

OctopusDeploy / Issues

| Public | Bug reports and known issues for Octopus Deploy and all related tools
https://octopus.com
162 stars 20 forks source link

Add support for opt-out behaviour to dotnet-script execution #8894

Closed IsaacCalligeros95 closed 1 week ago

IsaacCalligeros95 commented 1 week ago

Severity

Low

Version

2024.3.X

Latest Version

None

What happened?

In dotnet-script C# execution we've switched from allowing parallel execution in the old ScriptCs to isolated execution in dotnet-script. This is to resolve an issue where parallel execution of dotnet-script on the same target can lead to conflict issues on File Access when checking the Nuget.Config. Isolation is based on a mutex on the deployment target which includes any other cli commands that require isolation, namely python script.

This is being resolved with an opt-out feature toggle, setting Octopus.Action.Script.CSharp.BypassIsolation will allow dotnet-script to run in paralle. Note this is introduces the potential of failures if Nuget.Config access conflicts.

Reproduction

Run multiple dotnet-script C# steps on a single target in parallel.

Error and Stacktrace

No response

More Information

No response

Workaround

No response

octoreleasebot commented 1 week ago

Release Note: Added support for opting out of isolated execution on C# dotnet-script steps. To opt out set the variable Octopus.Action.Script.CSharp.BypassIsolation to true.

Octobob commented 1 week ago

:tada: The fix for this issue has been released in:

Release stream Release
2024.3 2024.3.5362