Hi all ! I spent some time looking into this and found that the massive job failing is telling us that the build dependency feature is now working! Which is because of every build that has dependency setting start from building upstream packages locally. That fills up the disk size on every build slaves. As I mentioned earlier, our CI build env is a sub-optimal design because of limited disk size on instances. I have no choice to split components equally on 4 slaves manually to ease the disk consumption.
Maybe I should start trying nexus server to put built jars there? Or I can specify an option to tell gradle to fetch jars directly from public maven instead of building upstream components locally? Thanks, Evans
