This message was deleted.
# configuration-cache
s
This message was deleted.
j
Do you mean a project waiting for another project to be configured? I think it is not possible. I suggested it should work like tasks work. If a project can be configured in parallel with another, they are configured in parallel, if not, it waits. Project isolation is great but too strict too
m
Do you mean a project waiting for another project to be configured?
Yes, some of my projects need input from the other ones
I suggested it should work like tasks work.
This is pretty much what I'm starting to think too. You have a tasks graph and a projects graph. Each one has inputs, can be up-to-date, etc...
Feels a bit weird though. Once we have projects graph, do we need another graph to "configure" the project graph ? 😅
graphs all the way down 🙈
j
Yes, some of my projects need input from the other ones
You will have to use the aggregator approach
m
Configurations and everything yea, this is what I'm doing at the moment.
It's getting users quite confused though, there are a lot of opportunities to do thing "wrong"
I wanted to provide a plugin function that configures multiple projects all at once as all this logic can be automated. But this obviously fails with project isolation
j
Is it not possible for your plugin to aggregate everything automatically under the hood instead of the user having to add the project to the configuration?
m
It's not just aggregating, it's doubly linking projects
Project A has a dependency on a task in project B Project B has a dependency on a task in project A
I'd like to expose this in a single place instead of the user having to manage configurations manually (and ultimately forgetting to update some of them, leaving the build in a bad state)
p
Did you find a solution?
m
Nope
I kind of gave up on easy project isolation. If users want project isolation, they'll have to configure everything the hard way with configurations and everything