infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-16030) Mesos is exhausting Jenkins resources
Date Wed, 21 Feb 2018 22:06:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tibor Digana closed INFRA-16030.
--------------------------------
    Resolution: Fixed

Now I do not see so many Mesos jobs executed in Jenkins CI.
Thx.

> Mesos is exhausting Jenkins resources
> -------------------------------------
>
>                 Key: INFRA-16030
>                 URL: https://issues.apache.org/jira/browse/INFRA-16030
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Tibor Digana
>            Priority: Major
>
> The problem is that Mesos is running periodically.
> You must really have a problem to find a free executor.
> Even if you do, your build composed of several runs of Maven takes too long time to complete.
> If you see the Mesos job you will see that it is triggered by a timer which means there
is no traditional commit trigger. Therefore this Mesos fails and always will fail with same
status which does not help at all.
> The Mesos timer behaves so that a bunch of runs is spread over several machines and when
they have finished the Mesos continues thereafter.
> Can you talk with the Mesos committers and ask them if they are aware of what is going
on and ask them to use commit trigger instead of timer?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message