We have those jobs configured to do that already, actually, which is why
the port conflicts are so surprising.
On 6/11/10 6:49 PM, Jane Young wrote:
> Justin,
>
> You can configure Hudson job to allocate port number for a specified
> variable or reserve the port number while it is running so it will
> block other builds when port is in-use. This will help resolve port
> conflicts test failures.
>
> Please take a look at the "Build Environment" section of the job
> configuration. There is a checkbox: "Assign unique TCP ports to
> avoid collisions".
>
> HTH,
> Jane
>
>
> Justin Lee wrote:
>> I've seen a lot of test failures on hudson lately because of ports
>> being in use by other processes. Is anyone else seeing those
>> failures? Are the zombie processes we need to clean out? I see this
>> especially on gerald and pigalle on the latest Grizzly_Integration
>> and webtier-dev-tests-v3-source jobs.
>
>