Can Hudson CI tool solve project dependencies others than trivial ones? For example, how can I set up scenario in which there are two independent modules (A, B) and module C dependent on A and B?
There's no way in my opinion:
- "Build others project" doesn't guarantee that A, B are built before C
- "Build after other projects are built" guarantee only "C is triggered after A or B" (A and B needed)
- Join plugin can solve this if one has ~ 3 modules. If there are modules A1, ....., A100 and C1, ....., C100 then it is supposed to write 100 additional Join triggers and issue 100 additional rebuilds of B (in other words, every B's reverse dependency needs rebuild of B). So in case that Join triggers cannot be trivially XML hacked and nonsense rebuilds of unchanged B cannot be skipped (is this possible?) it is unpractical.
So is there some way or some standard workaround to achieve this?