I also think using the fingerprint plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint) will be very useful
to track dependencies - i.e. this build failed because these dependencies are
not compatible...
*pretty cheap
Another problem caused by not using the "Block build when upstream project is
building" or "Block build when downstream project is building" in my post setup
is that Job A and Job B could end up running on the same slave. This would be
problematic (for me at least) since the artefacts of Job A
I'm also new here - but possibly facing similar problems (C#). I'm not sure
how exactly you expect the dependencies to be "handled", but I thought I would
post my opinion.
I am going for your option B "one job for each project?"
My current plan is to add "build other project" "post build tasks
