Is there a way to "cut" the task graph?

[sharpepd]

We are facing a challenge in using moon in a distributed pipeline.

If I have the following dependency graph:

:install -> :build -> :publish

The :build is done on one ci agent and then we need to do some other things (say manual validation) before we run the :publish task.
So :publish will be run on another agent.

We are relying on remote caching to get the outputs of :build onto the new agent, because :build is already done - we do not want to do it again. The problem we are facing is that :install must also be cached for this to work, but :install is very big and slow and we really don't need its artifacts on the :publish agent. The only thing we are interested in is the artifacts from :build.

In Gradle there is a command line option --exclude-task (https://docs.gradle.org/current/userguide/command_line_interface.html#sec:excluding_tasks_from_the_command_line).

This allows for the dependency graph to in effect be cut at certain points. I think I am looking for this feature in moon, unless there is already a way to achieve my goal.

Is there a solution for this in moon?

[milesj]

Do you want to ignore install for all agents? Or just subsequent ones?

If it's all, then you can use runInCI: skip, otherwise there is no way to do this currently.

[sharpepd]

Just the subsequent ones.

Agent 1:

:install -> :build

Agent 2:

:build(cached) -> :publish

And I an using moon run not moon ci in this case.

[milesj]

I can look into this for v2.