Yep, I think it's only useful (and likely to be maintained) if we actually use this on Jenkins. So that was my proposal. Basically give people a docker file so they can understand exactly what versions of everything we use for our reference build. And if they don't want to use docker directly, this will at least serve as an up-to-date list of packages/versions they should try to install locally in whatever environment they have.
- Patrick On Wed, Jan 21, 2015 at 5:42 AM, Will Benton <wi...@redhat.com> wrote: > ----- Original Message ----- >> From: "Patrick Wendell" <pwend...@gmail.com> >> To: "Sean Owen" <so...@cloudera.com> >> Cc: "dev" <dev@spark.apache.org>, "jay vyas" <jayunit100.apa...@gmail.com>, >> "Paolo Platter" >> <paolo.plat...@agilelab.it>, "Nicholas Chammas" >> <nicholas.cham...@gmail.com>, "Will Benton" <wi...@redhat.com> >> Sent: Wednesday, January 21, 2015 2:09:35 AM >> Subject: Re: Standardized Spark dev environment > >> But the issue is when users can't reproduce Jenkins failures. > > Yeah, to answer Sean's question, this was part of the problem I was trying to > solve. The other part was teasing out differences between the Fedora Java > environment and a more conventional Java environment. I agree with Sean (and > I think this is your suggestion as well, Patrick) that making the environment > Jenkins runs a standard image that is available for public consumption would > be useful in general. > > > > best, > wb --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
