Thanks Michael and Jim, It looks like adding to bin/bootstrap_build.sh makes the ub14-build-only job work fine, however, updating the impala-setup still doesn't seem to work. I submitted a pull request that was merged by Dimitris here: https://github.com/awleblang/impala-setup/commits/master
Also, the impala-setup chef logs don't seem to get printed in the jenkins console output. So I'm not sure if it's actually being run or not. On Wed, May 24, 2017 at 3:37 PM, Michael Brown <[email protected]> wrote: > Thanks Jim; I had forgotten bin/bootstrap_build.sh. > > On Wed, May 24, 2017 at 3:14 PM, Jim Apple <[email protected]> wrote: > > > I'd recommend against #2 using the node setup to install Impala > > dependencies. The only reason it installs openjdk is that Jenkins > > needs Java to talk to it. All of the other Impala dependencies are > > installed in the jobs themselves. > > > > On Wed, May 24, 2017 at 3:11 PM, Michael Brown <[email protected]> > wrote: > > >> Is there a way to add a new dependency to these machines? > > > > > > Our builds use two worker labels: > > > 1. ubuntu14.04-c4.4xlarge-gp2 > > > 2. ub14-build-only > > > > > > 1 uses https://github.com/awleblang/impala-setup, and I think you > should > > > add libffi to there. It's something you should do anyway so new users > get > > > set up with the right dependencies. > > > > > > 2 is a different story, but I see that at > > > http://jenkins.impala.io:8080/configure that worker is already > > installing a > > > JDK via apt-get. You could use a similar pattern to install libffi. > > >
