Closed artsiommiksiuk closed 6 days ago
Yeah local
was never meant to work both ways. I'll change this to a feature request.
Well, this might be problematic. As per documentation local
also overrides quite a set of options for task it did work for me e.g. because of conflicting cache and persistent options when referenced later as deps, so I'm not quite using it anymore.
Yeah local
is really only meant for dev servers/watchers/other tasks that run forever.
Gonna close this as local is going to be deprecated: https://moonrepo.dev/blog/moon-v1.28#new-task-presets
Describe the bug
I have a docker build process, and have two versions of a tasks - for local build and for ci build. Setting ci version to local: false still allows this task to be launched from local machine.
Steps to reproduce
Expected behavior
local: false
marked task (build-ci
) is not running locally.Environment
Additional context
Probably something like
localOnlyRun
,ciOnlyRun
options for a task will do better and more explicit.But the overall feeling is that some advanced tasks filtering capabilities for their execution is missing, like with https://github.com/moonrepo/moon/issues/1538 request.
Would be nice to have more general solution to be able to set of tasks (same name union based) where each tasks is marked with some attributes, and then moon selects which version of a task to run based on the attributes match, like [win, ci], [win, local], [arm, ci], [arm, local] and etc.