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 weight to 2 (unless one don't mind to wait).
On Thu, Feb 23, 2017 at 10:24 AM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
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 other random job, so let's be nice to each other ;)
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 didn't shut down correctly.
On 22 February 2017 at 21:48, Davide D'Alto <davide(a)hibernate.org> wrote:
> I've removed the Blue Ocean plugin.
> Let me know if there are still some problems.
> I've also configured the jobs so that the website jobs can be executed
> in parallel with the others.
> This should make publishing of a page faster.
> On Wed, Feb 22, 2017 at 10:47 AM, Davide D'Alto <davide(a)hibernate.org>
>> I'm going to remove the BlueOcean plugin from Ci.
>> Currently, when we receive an email because a build is failed, the
>> link to the job is wrong and it seems that BlueOcena is the cause.
>> I don't think anybody is actually using it but if there are some
>> objections, let me know.
> hibernate-dev mailing list
hibernate-dev mailing list