On 06/11/13 11:04, Andy Seaborne wrote:
Mystery:
(not important, just a mystery)
Why does Jena_New_Tests not show up under the Jena tab when all the
other jobs do? I thought it was just based on the job name. I don't
see a config option to associate jobs and projects.
https://builds.apache.org/view/H-L/view/Jena/
Mystery may be solved:
Jena_New_Tests is a downstream project of Jena_Development_Java6, only
built if JDJ6 succeeds and not run to it's own schedule.
I guess that Jenkins only shows the top projects and not the project
build downstream.
Our builds are timing out. Almost all the aborts are due to this is
some form or other. I've gone round increasing the timeout to 90 mins
but the fundamental problem is that the Jenkins server is overloaded.
It's not just us - partially its load, partially jobs seem to be getting
stuck on the Ubuntu slaves for days (despite timeouts) for reasons no
one is quite sure of at the moment (maybe fixed). A few stuck jobs
increases the congestion and the build queue starts getting longer. See
builds@.
I've turned off JIRA updating as it's looging unrelated build failures
against JIRA and set most jobs to only complain by email on the first
failure.
The ARM and Windows jobs are running OK.
Andy
