Hi all,
as you might know some time ago we were forced to
disable the win32 Hudson build due to excessive resource
consumption (NTFS over the virtualized disk was killing
the hosting box).
Good news, it's back. Arne took the time to upgrade the
virtualization layer with a more efficient one and we're
back in business. Kudos!
I plan to add the 2.0.x and 2.6.x builds shortly
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
This is great!
I notice the build is setup to build all the modules seperatly? Is this intentional? Just curious.
Andrea Aime wrote:
Hi all,
as you might know some time ago we were forced to
disable the win32 Hudson build due to excessive resource
consumption (NTFS over the virtualized disk was killing
the hosting box).Good news, it's back. Arne took the time to upgrade the
virtualization layer with a more efficient one and we're
back in business. Kudos!I plan to add the 2.0.x and 2.6.x builds shortly
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
This is great!
I notice the build is setup to build all the modules seperatly? Is this intentional? Just curious.
Eh... actually what you're seeing is the old Hudson I fear.
The new one is still being setup, I'll finish that tomorrow.
As for the separate build, I did not setup separate builds per
module.
I believe it's just sending a per message module for some reason,
but I may be wrong.
Will keep you posted on the Hudson restoring process
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
This is great!
I notice the build is setup to build all the modules seperatly? Is this intentional? Just curious.
Eh... actually what you're seeing is the old Hudson I fear.
The new one is still being setup, I'll finish that tomorrow.As for the separate build, I did not setup separate builds per
module.
I believe it's just sending a per message module for some reason,
but I may be wrong.Will keep you posted on the Hudson restoring process
Could this be the jobs being set up as maven jobs versus freestyle jobs?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
This is great!
I notice the build is setup to build all the modules seperatly? Is this intentional? Just curious.
Eh... actually what you're seeing is the old Hudson I fear.
The new one is still being setup, I'll finish that tomorrow.As for the separate build, I did not setup separate builds per
module.
I believe it's just sending a per message module for some reason,
but I may be wrong.Will keep you posted on the Hudson restoring process
Could this be the jobs being set up as maven jobs versus freestyle jobs?
Sounds likely. I'll look into it tomorrow and see if I can reduce the
number of mails.
The current setup has some distinctive advantages, the most important
is that it's very easy to find a failing test and its full stack
trace. I'd like to avoid loosing that.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.