[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Yong Guo commented on JENKINS-15156 Builds Disappear from Build History after Completion (updated) I just upgrade to 1.495, then the history goes back! 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-15156) Builds Disappear from Build History after Completion
Yong Guo commented on JENKINS-15156 Builds Disappear from Build History after Completion I have this problem after upgrading to 1.494. Master/Slave setup (all Linux box). Only the job create after upgrading has this problem. Those jobs created before upgrading work well. 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-15156) Builds Disappear from Build History after Completion
Yong Guo edited a comment on JENKINS-15156 Builds Disappear from Build History after Completion I have this problem after upgrading to 1.494. Master/Slave setup (all Linux box). Only the job create after upgrading has this problem. Those jobs created before upgrading work well. (updated) I find all the builds exists in the build directory. The problem is that they are not shown in the build history. 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-15824) SBT plugin does not support paths to sbt-launcher.jar to be configured per node
Yong Guo updated JENKINS-15824 SBT plugin does not support paths to sbt-launcher.jar to be configured per node Change By: Yong Guo (19/Dec/12 8:02 AM) Attachment: sbt_installation.patch Attachment: org.jvnet.hudson.plugins.SbtPluginBuilder.SbtInstaller.json 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-15824) SBT plugin does not support paths to sbt-launcher.jar to be configured per node
Yong Guo commented on JENKINS-15824 SBT plugin does not support paths to sbt-launcher.jar to be configured per node i've made some changes to implement this feature. i will create a pull request on github later. 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-13808) Status code 404 jenkins in v1.462 after login
Yong Guo commented on JENKINS-13808 Status code 404 jenkins in v1.462 after login same problem in v1.468. i use ldap authorization and matix-based security. after i added the users and set their permissions, they can log in normally. is there missing a default view for the user first login? 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-13808) Status code 404 jenkins in v1.462 after login
Yong Guo commented on JENKINS-13808 Status code 404 jenkins in v1.462 after login update: give overall read permission to anonymous user can avoid this problem. 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
