Hi, Can you have a go at suggesting a viable dev environment for non-LinkedIn staff? Perhaps the following would make sense to ask in this context.
- How much hardware would you throw at it if you didn't have access to a very large lab? - Have you ever run (for dev/testing) many components all on the same machine rather than distributing them across machines as the real scenario implies? I think the tests part of the repo implies this can be done, but not sure how bumpy that may be, you know, bumping into first-time co-location issues, or issues that aren't of interest for the real usage. Actually the two questions are a bit interrelated. Of course, this isn't to imply that patches would be accepted :) Thanks, Matan On Sat, Jan 12, 2013 at 7:11 AM, Jun Rao <jun...@gmail.com> wrote: > At LinkedIn, committers develop on mac or linux using either eclipse or > intellij. We have a testing cluster that constantly runs all our system > tests. > > Thanks, > > Jun > > On Fri, Jan 11, 2013 at 12:22 PM, S Ahmed <sahmed1...@gmail.com> wrote: > > > I'm very interesting in getting an inside peak as to how you guys go > about > > developing, updating, and adding new features to kafka. > > > > Kafka has allot of moving parts/dependencies, what is your usual workflow > > for developing, testing the kafka codebase? > > > > Do you rely on external vm's? > > Do you have helper scripts for quickly looking into the kafka logs? (like > > say python scripts for quick execution and turnaround times) > > > > Do you develop on a macbook, with scala, your compile times are pretty > long > > so any tips/tricks on avoiding it? (I'm guessing unit tests help as you > > don't have to load the entire stack) > > >
