On Thu, Jan 1, 2009 at 6:33 PM, Wes Wannemacher wrote:
Another consideration is whether or not to publish the builds to
> people.a.o. I mean, it's nice that the download is available to the
> public, but if we're setting this up, there may be no need. We could
> simply point people to
> http://
On Thu, 2009-01-01 at 20:28 -0700, Wendy Smoak wrote:
> On Thu, Jan 1, 2009 at 7:33 PM, Wes Wannemacher wrote:
>
> > So, I'd like to know what people think and if they have suggestions for
> > how they'd like to see this done. I'm not steadfastly sticking to Hudson
> > at this point, it just seem
On Thu, Jan 1, 2009 at 7:33 PM, Wes Wannemacher wrote:
> So, I'd like to know what people think and if they have suggestions for
> how they'd like to see this done. I'm not steadfastly sticking to Hudson
> at this point, it just seemed easy, so if someone thinks cruisecontrol,
> continuum or what
Well, it's not a requirement, but I was sort of thinking that the second
instance, that hosts our reference apps might need restarted frequently.
Imagine that it's open to the public and we get offensive names added in
the various people managers. I plan to use it to test. Each time we do a
release
why do we need 2 tomcat instances?
musachy
On Thu, Jan 1, 2009 at 9:33 PM, Wes Wannemacher wrote:
> So, Martin and I took the discussion off-list briefly about the
> nightlies and I learned a bunch about what we have and a few more things
> about what Apache can help us with.
>
> First off, I le
So, Martin and I took the discussion off-list briefly about the
nightlies and I learned a bunch about what we have and a few more things
about what Apache can help us with.
First off, I learned about Solaris Zones... It is a virtual machine,
like VMWare, but a bit different in the implementation.