|
||||||||
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 |
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
japear...@agiledigital.com.au (JIRA) Wed, 13 Jun 2012 20:17:23 -0700
- [JIRA] (JENKINS-13547) Jenkins runs e... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... th...@gmx.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... th...@gmx.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... japear...@agiledigital.com.au (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... th...@gmx.de (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... japear...@agiledigital.com.au (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... japear...@agiledigital.com.au (JIRA)
- [JIRA] (JENKINS-13547) Jenkins r... th...@gmx.de (JIRA)
Surely there is a better way? Maybe there should be an option to allow crowd to wait until the session times out or something? I'm guessing checking every request is just to see if the account is still allowed to login to Jenkins?