There are multiple problems with just spamming test patch with local repos. I've done a not insignificant amount of investigation in this space and there reasons why I didn't just slam it in even though I've been aware of the issue for a very long time. There are specific reasons why I want to tie this to Docker, at least for the Apache Jenkins runs. (No I'm not going to go into that now.)
I'm on my way back to SJC and will likely have code for Yetus tomorrow afternoon. Sent from my phone On Sep 22, 2015, at 11:55 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: >> >> >> Did anyone address Andrew's proposal to have one private repo per >> Jenkins executor? That seems like the simplest approach to me. It >> seems like that would only generate more network traffic in the case >> where a dependency changes, which should be relatively rare. >> >> We're blocked on YETUS-4, and then a corresponding Yetus release, and then > onboarding Hadoop to Yetus. > > Alternatively we can hack up test-patch.sh ourselves, since honestly I > think the above will take at least a month. Would love to be proven wrong > though.
