Thanks Davide!
All, we need your help now: please make sure that any job you enable
which uses any network port (like using Byteman, Arquillian, WildFly,
Databases, Elasticsearch, etc..) has set a "Job Weight" of 3.
When failing to do so, we'll see sporadic failures of both your job
and some othe
I suspect the WildFLy instance was still active because I've aborted
the job or restarted Jenkins at the wrong time while
appying the changes.
Speaking about the job weight, I didn't change the releases job, I'll
let the owners of each job to do that but I think it would make sense
to cahnge their
On 23 February 2017 at 12:24, Sanne Grinovero wrote:
> I think the setup is not perfect yet, as I've reviewed some failure
> reports and they seem caused by an already running WildFly instance on
> the same machine. So either we have a bad job configuration somewhere,
> or a WildFly instance which
Thanks Jordan!
Can you explain why we need to define the "managementPort" property?
Do you have a link to the issue maybe?
I'd like to understand that better, especially as we have several
other projects to patch.
Sanne
On 23 February 2017 at 11:09, Jordan Gigov wrote:
> On 23 February 2017 at
First the comment needs to be outside the property, otherwise it's not
detected as a text-only node.
Secondly managementPort has to be set, because while arquillian passes
on jboss.socket.binding.port-offset but does not take it into account.
Because of port-offset the management port is moved fro
