How can I force the CI trigger when one library changes but there is no direct dependency

[apescione]

I have a library in my monorepo and some projects use it not directly but through a CLI. Is there a way to force these projects to run their own CI when some files have touched into that library?
I tried dependOn, but it doesn't run the CI because moon doesn't see any touched files

[milesj]

Great question. There is a way around this right now using task deps (below), but I want to make this easier in the future.

In the shared library, you would basically add a noop task that has inputs on its files.

tasks:
  changed:
    command: 'noop'
    inputs: ['**/*']

And in all the other projects that "use" it, you can have tasks that depend on it.

tasks:
  build:
    command: '...'
    deps: ['library:changed']

[milesj]

That won't work, since moon ci is a task runner, so it only runs tasks. You would need a temporary task for the time being.

If we changed the task runner to always include the dependsOn project files in each task, then it would blow away all the granularity and fine tuning that task deps + inputs has to offer.

[frankswarm]

Hi, sorry for hijacking the conversation. I think it is somehow related, and I don't want to open an issue if it just a misconfiguration on my side.

I have seen in the docs and in this conversation the following:

moon ci will run downstream and upstream dependencies of an affected project, so if library was changed, the others should run also, but they have to be connected at the task layer.

I'm currently facing an issue where I have more than one level of dependency. Let's say that I have projects A, B and C, and A depends on B, and B depends on C. They are dependents at the task layer also.

When I make changes on project C only and execute moon ci the tasks on C and B are executed, but not the task on A. Is the execution limited to direct downstream dependencies? Is this behavior expected?

I'm using moon (1.22.9).

[milesj]

Yeah, I believe it's only direct dependencies at the moment. We need to improve it a bit to pass more context through.

[frankswarm]

Are you planning to add this feature? Should I create an issue with the feature request?

[milesj]

Yeah but I can't really say when it would land. There's a long backlog of features.