www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp Ottlinger (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-8221) Change Jenkins configuration - longer timeout values / proper JDK grouping for Java8
Date Wed, 20 Aug 2014 20:04:26 GMT
Philipp Ottlinger created INFRA-8221:
----------------------------------------

             Summary: Change Jenkins configuration - longer timeout values / proper JDK grouping
for Java8
                 Key: INFRA-8221
                 URL: https://issues.apache.org/jira/browse/INFRA-8221
             Project: Infrastructure
          Issue Type: Improvement
          Components: Jenkins
         Environment: https://builds.apache.org/view/A-D/view/Creadur/
            Reporter: Philipp Ottlinger
            Priority: Critical


h3. Longer session timeout values for users logged in to Jenkins
Since I'm trying to establish some builds for creadur under https://builds.apache.org/view/A-D/view/Creadur/
and the builds wait in the build queue for roughly 2-3 hourse before running in minutes I'd
like to have longer _timeout value_ for Jenkins.
I seem to get logged out pretty fast - 30min?

Since I trigger the build and check for any progress within the next hours it costs some more
clicks to relogin and change to our tab .... https://builds.apache.org/view/A-D/view/Creadur/
is not publicly visible and I get redirected to the Jenkins main page after logging in after
session timeouts. 

A session timeout of 4 hours should be feasable to catch our slowly running builds.

h3. JDK streamlining
Currently there is a wide variety of JDKs available to run jobs on. It's not really clear
whether all of the JDKs are installed on all build slaves.
To my mind it would ease JDK selection if there were a 'JDK 1.8 latest' that links to the
currently available Oracle JDK8.

This would ease batch configuring jobs and most probably make it easier to deploy JDK updates
on all slaves for you guys.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message