[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
David Barri commented on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded Ignore my previous comment. Seems to just be luck of the draw when Jenkins is restarted. Workaround: Just keep restarting until you get lucky. 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-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
David Barri updated JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded Change By: David Barri (25/Mar/13 5:45 AM) Attachment: jenkins-12124.log 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-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
David Barri commented on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded Upgrading Analysis Collector Plugin from 1.34 to 1.35 caused this problem for me, on both 1.502 and 1.506 versions of Jenkins. Downgrading back to 1.34 got my builds visible again. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
David Barri commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Wow the new version of this plugin completely broke my jobs. I have a single symlink from one directory to another (non-recursive) and my builds refuse to update, showing the same "Cannot delete file" error. I don't think JGit handles symlinks at all does it? I remember reading something a while back about the JGit team not planning on building in symlink support at all until Java gets native support for symlinks. If that's still the case then migrating to JGit is a disastrous idea for those of us in the Linux world. And what's this about Git CLI being fragile, yada yada? Git CLI has a porcelain mode so that tools can rely on it without worrying about version or output fragility. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
David Barri commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly My god https://bugs.eclipse.org/bugs/show_bug.cgi?id=354367 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-13559) Allow extra parameters when running Android monkey tester
David Barri commented on JENKINS-13559 Allow extra parameters when running Android monkey tester FYI a workaround is to add your additional parameters to the plugin's Package ID field. For example I set my package ID to golly.bpm --pct-trackball 0 --ignore-native-crashes --randomize-throttle. And in the logs I see it run monkey like this: /opt/android-sdk/platform-tools/adb -s localhost:53355 shell monkey -v -v -p golly.bpm --pct-trackball 0 --ignore-native-crashes --randomize-throttle -s 262851713055245828 --throttle 0 5 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-15903) Broken URL for Monkey result icons
David Barri created JENKINS-15903 Broken URL for Monkey result icons Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 23/Nov/12 4:30 AM Description: Plugin is generating incorrect URL for Monkey icons (ie. icon displayed to indicate Monkey success or failure on build). The URL it generates is: http://xxx:yyy/static/8c6c454b/static/8c6c454b/plugin/android-emulator/icons/monkey-happy_48x48.png As you can see static/8c6c454b is repeated twice. Changing it to once works. Environment: Jenkins v1.490 android-emulator plugin v2.6 Linux 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux Project: Jenkins Priority: Minor Reporter: David Barri 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
David Barri commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis I'm having this issue too. The relevant part of my POM looks like this: plugin groupIdorg.jacoco/groupId artifactIdjacoco-maven-plugin/artifactId version0.6.0.201210061924/version executions execution idcoverage-agent/id phaseprocess-test-classes/phase goals goalprepare-agent/goal /goals /execution execution idcoverage-report/id phasetest/phase goals goalreport/goal /goals /execution /executions configuration excludes !-- Exclude classes generated by AndroidAnnotations -- exclude**/*_.*/exclude exclude**/*_$*/exclude /excludes /configuration /plugin When I generate a Jacoco HTML report, classes that end in an underscore like ExampleActivity_ do not appear because of the exclude settings in my POM. However from Jenkins all of those classes that the Maven build excludes are visible again. My Jenkins settings for this plugin are the defaults. Thanks! David 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
