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
Just noticed that global dynamic variables are evaluated each time a task is run.
This can indeed become a performance problem. It could at least be documented.
I don't see many workarounds in the meantime.
Commands that take time should not be used in global dynamic variables but rather sub-commands or task dependencies.
Or, you could add conditions in the expression itself. Local variables aren't available, but, for example, the TASK variable is:
This is kind of ugly and cumbersome, but can be used with task namespaces in order to confine the problem to the tasks that actually need that variable.
I suppose long running command results could also be cached, when possible.
Only load global variables with
SH
when the task needs it:Other tasks that don't need the variable should not have it loaded
The text was updated successfully, but these errors were encountered: