Re: [jboss-as7-dev] port conflict with AS7 runs
You have tied your job to UNIX-slim label which contains slaves with multiple
executors. So the most easy way how to awoid conflicts is to tie the job to
another label (e.g. "linux"). Most of the slaves have only one executor and
therefore there won't be any conflicts as the slave will always run only one
job.
More complicated setup could be setup "Build after other projects are built"
build trigger and specify colliding job. However if you have also configured
SCM polling trigger and both jobs poll same SCM, this setup is useless as
build triggers act independetly.
I.e. I would recommend to change the job labels.
Can I some how queue the jobs that I know will conflict when run on
the
same machine. We have 'localhost' and port numbers hard coded all over
the shop in the testsuite. So I guess the safest would be to run AS jobs
sequentially on the same machine.
-thomas
On 10/12/2011 12:19 PM, Vojtech Juranek wrote:
> Hi Thomas,
> most of the slaves have set up enviroment variables $MYTESTIP_{1,2} (in
> case of dev09, where your last build run, it's 10.16.93.41 and
> 10.16.93.42, also available under $MYTESTIPS) so you can bind each
> instance to different IP (at least AFAIK EAP QA guys use it to avoid
> such conflits). Another solution is to shift all ports of the instance
> (but I don't remember the option for it from top of my head and I'm also
> not sure if this feature is present in AS7).
>
> Or you meant, that you run your build, but there was another (different)
> build running on the same machines, which caused the conflict?
>
> Cheers
> Vojta
>
>> Hi Vojtech,
>>
>> I have several test runs fail
>> <https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-as1601/
>> 16/ console> because they simultaneously run the AS7 testsuite on the
>> same machine. What is the best way to avoid these conflicts? I assume
>> that 'localhost' is hardcoded into the testsuite.
>>
>> cheers
>> -thomas