[JIRA] [ruby-runtime] (JENKINS-16284) Failing to launch SSH slave agents after upgrade to 1.498
A K commented on JENKINS-16284 Failing to launch SSH slave agents after upgrade to 1.498 We had issues with our ssh slaves not working (ie. you'd go to start it and it would just hang, no logs, no attempts to login noted on slaves), it turns out that it was the ruby-runtime plugin that was causing all the problems. Simply removing it and restarting, fixed the issues. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Some testing with my own builds shows that the trigger/difference for causing the "java.io.NotSerializableException" is when the advanced setting "Merge before build" is checked off and filled in. Git operations without this seem to work fine. *Haven't tested extensively of course 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Some testing with my own builds shows that the trigger/difference for causing the "java.io.NotSerializableException" is when the advanced setting "Merge before build" is checked off and filled in. Git operations without this seem to work fine. *Haven't tested extensively of course *Edit: This confirms what David Walend commented on earlier. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Additionally, I was able to reproduce this behaviour on OSX and Linux slaves, both 64-bit. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Excellent. I am glad to hear that. (I saw the new 1.0.5 come out but didn't have a chance to test it). The solution is also comforting/as-expected given the previous release notes, so I am optimistic it is fixed. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K created JENKINS-17242 pushes no longer being recorded in destination repository Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 15/Mar/13 10:38 PM Description: Rolled fwd jenkins installation to use latest git plugin, and now post-build task of pushing no longer registers in repository. It says it is doing it, but checking the repository confirms that the branch has not been updated. No changes were made to project, it just stopped working. Environment: Linux Ubuntu jdk6 Project: Jenkins Priority: Major Reporter: A K 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Pushing HEAD to branch master of test_local repository Opening connection Counting objects Finding sources Writing objects Pushing HEAD to branch master at repo test_local Opening connection Counting objects Finding sources Writing objects Except, master doesn't update. :S 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K updated JENKINS-17242 pushes no longer being recorded in destination repository Change By: A K (15/Mar/13 10:49 PM) Priority: Major Blocker 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Rolling back to Git Plugin version 1.1.26, and restarting jenkins fixed the problem. fyi. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16051) CI Game scoring
A K created JENKINS-16051 CI Game scoring Issue Type: Bug Assignee: redsolo Components: ci-game Created: 05/Dec/12 9:52 PM Description: CI Game version - 1.19. On fixing a broken build, only 1 point is awarded, even if many fixes were put through for code styling as well. Project: Jenkins Priority: Minor Reporter: A K 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-13635) Backup warnings when performing tar.gz
A K created JENKINS-13635: - Summary: Backup warnings when performing tar.gz Key: JENKINS-13635 URL: https://issues.jenkins-ci.org/browse/JENKINS-13635 Project: Jenkins Issue Type: Bug Components: periodicbackup Environment: Jenkins 1.459, Running on Ubuntu Linux. Periodic Backup Version 1.1 Reporter: A K Priority: Minor The jenkins log is filled with lines like the following (whenever it goes to do a backup): [INFO] Building tar: ... ... [WARNING] Entry: jobs/.../.../.../... longer than 100 characters ... The backups appear to be completing still, but am not 100% sure if the tar files are corrupt or not. Doing my own minor research indicates that adding the '-E' flag will allow for longer filenames, so perhaps this is something that should be added to the plugin? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
