|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I'm seeing something very similar on 1.517 where all of the history and status for some, but not all jobs will just disappear. I have an identical server that has no build slaves where this issue has not been reported, however on a server that has multiple build slaves, and this is being encountered at least once a week, possibly twice a week much to my developer's frustrations.
All slaves are JNLP launched. All hosts are Linux. OpenJDK 1.6. Build history files can be found on disk on the master, but are not listed in the gui. Jobs are configured to retain artifacts for 5 builds, and history for 20 builds. Matrix permissions are in use.
ant
credentials 1.4
cvs 2.8
email-ext 2.28
external monitor job 1.1
git 1.3.0
git-client 1.0.5
javadoc 1.1
jira 1.35
mailer 1.4
maven-plugin 1.512
pam-auth 1.0
ssh-credentials 0.3
ssh-slaves 0.25
jenkins translation 1.10
token-macro 1.6