Re: Jenkins networking / port contention

Multiple instances of test runs are usually running in parallel, so they would need to bind to different ports. On Friday, July 1, 2016, Cody Koeninger wrote: > Thanks for the response. I'm talking about test code that starts up > embedded network services for integration

Re: Jenkins networking / port contention

gotcha... adding @joshrosen directly who might be of more assistance... :) On Fri, Jul 1, 2016 at 9:38 AM, Cody Koeninger wrote: > Thanks for the response. I'm talking about test code that starts up > embedded network services for integration testing. > > KafkaTestUtils in

Re: Jenkins networking / port contention

Thanks for the response. I'm talking about test code that starts up embedded network services for integration testing. KafkaTestUtils in particular always attempts to start a kafka broker on the standard port, 9092. Util.startServiceInPort is intended to pick a higher port if the starting one

Re: Jenkins networking / port contention

i assume you're talking about zinc ports? the tests are designed to run one at a time on randomized ports -- no containerization. we're on bare metal. the test launch code executes this for each build: # Generate random point for Zinc export ZINC_PORT ZINC_PORT=$(python -S -c "import random;

Jenkins networking / port contention

Can someone familiar with amplab's jenkins setup clarify whether all tests running at a given time are competing for network ports, or whether there's some sort of containerization being done? Based on the use of Utils.startServiceOnPort in the tests, I'd assume the former.