You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2013/04/20 00:15:16 UTC

[jira] [Commented] (INFRA-6177) Many builds encountering starvation on Jenkins

    [ https://issues.apache.org/jira/browse/INFRA-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636938#comment-13636938 ] 

#asfinfra IRC Bot commented on INFRA-6177:
------------------------------------------

<gmcdonald> this sort of thing gets discussed on the builds@ list

                
> Many builds encountering starvation on Jenkins
> ----------------------------------------------
>
>                 Key: INFRA-6177
>                 URL: https://issues.apache.org/jira/browse/INFRA-6177
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jenkins
>            Reporter: Rob Vesse
>
> I've noticed that lately there seems to be an increasing amount of build starvation happening on Jenkins, from what I can glean by what I can see of the build queue this is down to two main issues:
> 1 - General lack of slaves for generic tags
> 2 - Builds running ridiculously long and monopolizing resources
> For example for builds tagged ubuntu there should be 6 servers (ubuntu1-ubuntu6) but right now only ubuntu4 and ubuntu6 are running
> In terms of long running builds there is one in particular I always seem to see hogging resources (https://builds.apache.org/job/Qpid-Java-Java-MMS-TestMatrix/) which when it succeeds takes 22 hours to run which seems excessive.
> While I appreciate the ASF has limited build and infrastructure resources having the build servers up more reliably and addressing excessively long builds (whether by talking to the responsible projects or by imposing some limit on build time) would go a long way to making things smoother for Apache developers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira