My solution to this, was to do it within my main project :
- Iterate a list of dependencies
- Clone them into the project
- Look for a standard named bash script in each one and call it.
- The standard named script calls other bash scripts as needed
But this does not cascade, and it misses out on the circle.yml structure/process.
So I agree with this feature request, but . . .
In my case, the subprojects are packages that can be unit tested outside the parent. However, functional testing without the containing product is too hard to be worth the effort. This wouldn’t be the case for everyone, but is something to consider when designing a listener trigger as you propose,
You’d want the parent to start building, trigger the children, wait on their completion before importing their latest versions and only then continue with functional testing.
(PS : My code for the dependency iterator is public, if anyone’s interested, just say so and I’ll post the links.)