On Mon, Nov 22, 2010 at 11:18, Eric Charles <[email protected]> wrote: > Oops, didn't read your last paragraph... > Did you plan to setup and deploy your self? (just to know)
Basically yes, in a way. Let's wait and see what I will come up with. I just wonder what a good initial configuration would be. Plain vanilla from trunk? Bernd > Tks, > Eric > > On 22/11/2010 10:51, Eric Charles wrote: >> >> Hi Bernd, >> >> That sound really great! >> If OK to everyone, I could setup something to automate the tests based on >> postage. >> >> Do you plan to send ssh account to james committers? >> Take your time, there's really no emergency, I'm full busy for now. >> >> Tks, >> >> Eric >> >> >> On 19/11/2010 12:04, Bernd Fondermann wrote: >>> >>> On Thu, Nov 18, 2010 at 18:04, Eric Charles<[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> The ideal would be to have windows and linux (virtual) server with jdk >>>> 1.5 >>>> and enough memory (2GB?). >>>> >>>> I don't know if apache or Bernd's infra can offer this. >>> >>> james-testing.de would be a Debian machine running 1.5 (or 1.6 >>> alternatively). >>> >>>> I was also thinking to benchmarks (james/windows vs james/linux, james >>>> vs >>>> other mails servers, james maildir vs james jpa,...), so Bernd's infra >>>> would >>>> be best suited to changes,... >>>> >>>> On these operating systems, we could deploy continuum (or hudson?) to >>>> trigger/automate the tests (being called via maven). >>> >>> We have at least Hudson running at the ASF. >>> >>>> In first instance (maybe after), i don't see the need to create real >>>> james >>>> accounts for committers,... >>>> >>>> I have happily used postage a few times (when we were searching for oom >>>> on >>>> smtp), but before going to that "integration testing" level, I still >>>> think >>>> that a lower level provided by mpt would be welcome (but I don't know if >>>> mpt >>>> is already usable). >>>> >>>> We could imagine start with a postage maven plugin that would load james >>>> in >>>> memory (without the need for a real distribution on disk). This would be >>>> a >>>> challenge in the current configuration, but feasible (load spring and >>>> conf >>>> from classpath). This would be also a real added value to have an >>>> "embeddable James server". >>> >>> For james-testing.de I'm currently thinking of a production-like >>> setup. It would run selected builds, not nightlies, more the >>> milestones category. RAM would be around 1GB. >>> Running postage against it would be a good app I think. >>> >>> Bernd >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
