I have never actually tried to run a full build recently. It takes a long time and usually isn't what is needed for a particular change. FWIW I view Beam at this point as a mini-monorepo, so each directory and target can be healthy/unhealthy on its own.
But it does seem like we should at least know what is unhealthy and why. Have you been filing Jiras about the failures? Are they predictable? Are they targets that pass in Jenkins but not in vanilla build? That would mean our Jenkins environment is too rich and should be slimmed down probably. Kenn On Sun, Mar 10, 2019 at 7:05 PM Michael Luckey <[email protected]> wrote: > Hi, > > while fiddling with beams release process and trying to get that working > on my machine, I again stumbled about 'gradlew build' > > Till now I am unable to get a full build run successfully on my machine. > Keeps failing. After setting up a clean docker instance and trying to run > there, I also failed miserably. Which of kind is expected as part of the > tests rely on docker itself which probably does not work out of the box. > But apart from these expected failures, there were also tons of other > failures. Need to setup a full blown vm and test again, but wanted to ask > here first as after looking into Jenkins setup, I was also unable to find a > job which actually executes a full build. > > So I am wondering, whether > - anyone is actually able to successfully execute a full build (preferable > without build cache) > - it is intended we do only run a 'gradlew build' during release on > release managers box > - if that full build is somehow implicit in Jenkins setup, and I am just > not finding my way to the job/list of jobs which execute this full build > > Any help/insights appreciated here. > > michel > > >
