[JIRA] [subversion] (JENKINS-16736) SVN triggers build without any SCM change
kutzi commented on JENKINS-16736 SVN triggers build without any SCM change Are the clocks of your Jenkins and your SVN servers in sync? 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] [subversion] (JENKINS-16736) SVN triggers build without any SCM change
Alex Vesely commented on JENKINS-16736 SVN triggers build without any SCM change I am also seeing this issue on several of my jobs. Jenkins 1.506, Subversion plugin 1.45. I have a chain of jobs (job A polls SVN and performs the checkout, then triggers job B). As soon as job B starts, job A is already in the queue again, even though the SVN was untouched. This happens many times in a row. But once I kill a checkout job (or just remove it from the queue), this activity stops, which is also suspicious. Here are the SCM polling logs (they are 100% similar in many builds that run one after another): Received SCM poll call on linux_slave for job_A on Apr 9, 2013 9:20:09 AM https:///external1 is at revision 19,227 https:///external2 is at revision 19,180 (changed from 17,206) https:///external3 is at revision 13,530 https:///external4 is at revision 17,897 (changed from 17,188) https:///trunk is at revision 19,241 Done. Took 0.79 sec Changes found What can I do to debug this behavior? Where does Jenkins keep information about the revision it has seen at the latest build? Perhaps the file got locked somehow? 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] [m2release] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Patrick McKeown commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I'm using the latest snapshot and the fix is working, thanks! 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] [publish-over-ssh] (JENKINS-17319) SSH sites disappear
Patrick McKeown commented on JENKINS-17319 SSH sites disappear We just upgraded to 1.509 and are experiencing the same issue. Is a fix in the works or are you dependent on a change to Jenkins core? 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] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)
Andrew Zellman edited a comment on JENKINS-17517 Support for dynamic skins (a la JellyBean devices) I'm actually using MonkeyRunner to press the buttons, but I need the natural UI that is present on most JellyBean devices, not hardware buttons that appear outside the emulator window. Note the soft controls at the bottom of only one of the uploaded pictures. 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] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)
Andrew Zellman updated JENKINS-17517 Support for dynamic skins (a la JellyBean devices) Note the soft controls at the bottom. Change By: Andrew Zellman (09/Apr/13 12:38 AM) Attachment: WhatIGot.png Attachment: WhatIWant.png 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] [android-emulator] (JENKINS-17522) Ability to start emulator only if Android build succeeds
Austyn Mahoney commented on JENKINS-17522 Ability to start emulator only if Android build succeeds It would be great to add this for ease of use, but I understand that this is implemented as a build wrapper and not a step. The downstream pattern should work fine for now, especially if we decide to use matrix jobs. Thanks. 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] [testlink] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Bruno P. Kinoshita stopped work on JENKINS-8636 TestLink Plugin FATAL: Error creating test project Change By: Bruno P. Kinoshita (08/Apr/13 11:51 PM) Status: In Progress Open 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] [testlink] (JENKINS-8636) TestLink Plugin FATAL: Error creating test project
Bruno P. Kinoshita commented on JENKINS-8636 TestLink Plugin FATAL: Error creating test project There was similar error, but the message was different. If you find similar issue again, please attach as much information as possible. In case you're having problems with the data exchanged between TestLink and Jenkins, in order to help, I might need you to sniff the connection between Jenkins and TL (using QDPF, Wireshark, or some other tool of your preference). I'm cutting a new release anyway, but feel free to add any comment here or let me know if you find any 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] [testlink] (JENKINS-15937) TestLink Plugin prevents Jenkins from parsing Jobs
Bruno P. Kinoshita stopped work on JENKINS-15937 TestLink Plugin prevents Jenkins from parsing Jobs Change By: Bruno P. Kinoshita (08/Apr/13 11:49 PM) Status: In Progress Open 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] [testlink] (JENKINS-15937) TestLink Plugin prevents Jenkins from parsing Jobs
Bruno P. Kinoshita commented on JENKINS-15937 TestLink Plugin prevents Jenkins from parsing Jobs Postponed to 3.4. If possible, please also include Jenkins and plug-ins version. Not sure if this information was already here (I apologize if so). Thanks! 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] [testlink] (JENKINS-17147) The configuration for testng method name and data provider is not saved
SCM/JIRA link daemon commented on JENKINS-17147 The configuration for testng method name and data provider is not saved Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/hudson/plugins/testlink/result/TestNGMethodNameDataProviderNameResultSeeker/config.jelly http://jenkins-ci.org/commit/testlink-plugin/a2b2403c6b28f9290b4606d1bb416f8c4abceb8e Log: [FIXED JENKINS-17147] 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] [testlink] (JENKINS-17147) The configuration for testng method name and data provider is not saved
SCM/JIRA link daemon resolved JENKINS-17147 as Fixed The configuration for testng method name and data provider is not saved Change By: SCM/JIRA link daemon (08/Apr/13 11:47 PM) Status: In Progress Resolved Resolution: 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] [testlink] (JENKINS-17147) The configuration for testng method name and data provider is not saved
Bruno P. Kinoshita commented on JENKINS-17147 The configuration for testng method name and data provider is not saved Issue confirmed. Working on a fix. Thanks for reporting! 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] [testlink] (JENKINS-17146) Test link plugin is not looking trough my suite name options in testNG
Bruno P. Kinoshita stopped work on JENKINS-17146 Test link plugin is not looking trough my suite name options in testNG Change By: Bruno P. Kinoshita (08/Apr/13 11:39 PM) Status: In Progress Open 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] [testlink] (JENKINS-17146) Test link plugin is not looking trough my suite name options in testNG
Bruno P. Kinoshita commented on JENKINS-17146 Test link plugin is not looking trough my suite name options in testNG Cutting a new release tomorrow night. Postponing this issue for 3.4. 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita stopped work on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Change By: Bruno P. Kinoshita (08/Apr/13 11:36 PM) Status: In Progress Open 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita updated JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Screen Shots (including TL and Jenkins) Change By: Bruno P. Kinoshita (08/Apr/13 11:35 PM) Attachment: attachments.zip 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita updated JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Sample project. Java project, built with Maven 3.0.5. Dependencies: JSoup and TestNG. Produces testng-results.xml, used in TL result seeking strategy. Change By: Bruno P. Kinoshita (08/Apr/13 11:36 PM) Attachment: yahoonews-test.zip 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Hi Jeff, I just tested a simple integration. I'll attach a sample project, and some screen shots. I'm sending these files to another user that was having trouble setting up similar integration. It uses TestNG, Java, Maven, TL 1.9.6 and Jenkins+plugin. I believe it will be helpful. I'm cutting a new release Tuesday night (-3GMT), so if you find any bug and could report before that, I'll be happy to include it in this release (in case we can fix the issue before that). Many thanks! Bruno 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] [plugin] (JENKINS-17528) Discard Old Builds plugin throws java.lang.UnsupportedOperationException
Bruce Edge created JENKINS-17528 Discard Old Builds plugin throws java.lang.UnsupportedOperationException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 08/Apr/13 10:51 PM Description: Split as new bug from https://issues.jenkins-ci.org/browse/JENKINS-16979 Also reported here: http://stackoverflow.com/questions/15268736/error-publisher-org-jenkinsci-plugins-discardbuild-discardbuildpublisher-aborte If a post-build action to 'Discard Old Builds' is added, this always results: Archiving artifacts Discard old builds... ERROR: Publisher org.jenkinsci.plugins.discardbuild.DiscardBuildPublisher aborted due to exception java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:148) at java.util.AbstractList.add(AbstractList.java:108) at org.jenkinsci.plugins.discardbuild.DiscardBuildPublisher.perform(DiscardBuildPublisher.java:148) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:720) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) and the build fails. Environment: Ubuntu 12.04.1 64 Jenkins 1.510 Discard Old Build plugin 1.02 Project: Jenkins Priority: Major Reporter: Bruce Edge 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] [core] (JENKINS-16979) "Discard old builds" broken in 1.503
Bruce Edge commented on JENKINS-16979 "Discard old builds" broken in 1.503 Done, thanks. https://issues.jenkins-ci.org/browse/JENKINS-17528 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] [android-emulator] (JENKINS-17522) Ability to start emulator only if Android build succeeds
Christopher Orr resolved JENKINS-17522 as Postponed Ability to start emulator only if Android build succeeds I'd say that it's really unlikely that this would get implemented any time soon. Most people use two jobs and the usual Jenkins downstream build pattern for this purpose. i.e. The first job builds the APK(s) and can fail fast if something goes wrong. If successful, it starts a downstream build of the second job, which starts an emulator, pulls the APK(s) from the first build and runs the tests etc. This is also very useful for matrix jobs, where you want to test on multiple Android platforms, languages, screen densities etc., as you only need to build the APK once in a freestyle job, then kick off a downstream matrix job which runs the various different emulators. Change By: Christopher Orr (08/Apr/13 10:42 PM) Status: Open Resolved Resolution: Postponed 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] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)
Christopher Orr commented on JENKINS-17517 Support for dynamic skins (a la JellyBean devices) Sorry, I'm still kind of unclear on what the use case is. You're using Jenkins to automatically generate and start emulators, but then want to manually click on the Menu button? Is that right? If you want to manually press the Menu button, you can use the F2 key on your keyboard instead, regardless of whether the extra UI is there. If you want to press the Menu button from an automated test, that should still work fine, even on emulators like the Nexus 7 which don't have hardware keyboards. Also, I tested just now with (and also without) a custom hardware property called "skin.dynamic" set to "yes", and it worked as expected (i.e. the extra UI at the side of the emulator window appeared (or didn't)). 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Bruno P. Kinoshita commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Hi Jeff, http://www.teamst.org/forum/viewtopic.php?f=9&t=1710 While you check if you have any custom status, I'll prepare a test project, with TL 1.9.6 (sorry, I now have only the latest version), Jenkins TestLink Plug-in (dev version, that'll be released on Tuesday), and TestNG. Any special characteristics in your TestNG tests? Thanks! 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] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Gregory Boissinot resolved JENKINS-17468 as Fixed NullPointerException in URLTrigger.getFTPResponse during startup Change By: Gregory Boissinot (08/Apr/13 10:15 PM) Status: Open Resolved Resolution: 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] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
SCM/JIRA link daemon commented on JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java http://jenkins-ci.org/commit/urltrigger-plugin/147b1f01c6fde1d97ebc8934e6fbec942e1ed969 Log: Fix JENKINS-17468 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] [repository] (JENKINS-17527) last successful build not properly updating
Chris Cooper created JENKINS-17527 last successful build not properly updating Issue Type: Bug Affects Versions: current Assignee: magnayn Components: repository Created: 08/Apr/13 9:50 PM Description: The current version of this plugin is completely broken for me, and I had to downgrade back to 0.11 in order to continue to use it. After 0.11 the plugin must have changed something about the URL being used for the artifacts to be retrieved from because my builds are no longer pulling the latest upstream artifacts. They are stuck using a build from almost 2 weeks ago. As soon as I downgraded to 0.11 from 1.0 it began to work again. Please advise any additional information I can provide for this issue to be solved. I noticed in the log output for the build that the URL used to be something like /jenkins/plugin/repository/project/geneva/LastSuccessful/repository/ and now it is something like this /jenkins/plugin/repository/project/geneva/Build/100/repository The former URL has files/directories in it for the artifact I expect, but the latter does not Environment: centos6 jenkins-1.509 Project: Jenkins Priority: Blocker Reporter: Chris Cooper 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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
jpschewe commented on JENKINS-17520 xUnit check for old tests is too short If I disable the check,then I'm fine. I always do a clean, so this is fine for me. But you'll probably want to increase the timeout or make it configurable to make it useful. If a system is loaded it could be a few seconds between when cppcheck is run and the plugin is executed. 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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
Gregory Boissinot commented on JENKINS-17520 xUnit check for old tests is too short I did a mistake. 3 seconds is the delay between the start build time and the last modified date of the report file. The objective is to not take reports from previous build if you don't have do a clean. Is it still a issue for you? 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] [xunit] (JENKINS-17491) xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception
Gregory Boissinot commented on JENKINS-17491 xUnit v1.52 fails with ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception It seems to be a JDK vendor issue. I'm afraid I don't know no more information. 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] [testlink] (JENKINS-16898) Testlink plugin exception setting status with TestNG Result Seeker
Jeff Rodgers commented on JENKINS-16898 Testlink plugin exception setting status with TestNG Result Seeker Bruno, I did not change any of the execution statuses (I didn't know you could do that). Is is possible that the Tutorial changed something? Where would I look to see the list of execution status types? 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] [publish-over-cifs] (JENKINS-17112) Publish over CIFS shares do not persist
David Brossard commented on JENKINS-17112 Publish over CIFS shares do not persist What is the status of this code? Is it up to the plug-in developers to fix their code or is a fix forthcoming for jenkins itself? As the change to xstream seems to have broken several common plug-ins this seems like a critical issue. Thanks 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] [xunit] (JENKINS-17525) XUnit plugin fails to convert all tests to JUnit file.
Ben Vaughan commented on JENKINS-17525 XUnit plugin fails to convert all tests to JUnit file. The attached XML file was generated by xUnit.net with the /nunit option set. 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] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Pedro Rodriguez created JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2013-04-08 at 5.00.36 PM.png Components: core Created: 08/Apr/13 9:12 PM Description: Happens semi-random, but whenever I leave the Jenkins page for an amount of time and then come back and hit refresh, the CSS seems to break (see attached image). Hitting refresh again does NOT fix it. However, holding shift while refreshing (forced refresh) fixes the issue and the page goes back to looking normal (hitting normal refresh works fine then). I've tried it in different browsers (and even a co-worker's computer) and it is happening there too. Project: Jenkins Priority: Minor Reporter: Pedro Rodriguez 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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
jpschewe commented on JENKINS-17520 xUnit check for old tests is too short The time at the top of the job is Apr 8, 2013 1:40:36 PM. This particular build took 59 seconds. I found the checkbox, that's why I marked this trival for priority. I'm able to work around this by checking the box. 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] [xunit] (JENKINS-17525) XUnit plugin fails to convert all tests to JUnit file.
Ben Vaughan created JENKINS-17525 XUnit plugin fails to convert all tests to JUnit file. Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: SomeProject.Contracts.Tests.dll.xml Components: xunit Created: 08/Apr/13 9:03 PM Description: Some of our XUnit files are not fully converting to JUnit files. In the attached XUnit file all of the test suites show up except: SomeProject.Contracts.Tests.CustomerTests SomeProject.Contracts.Tests.DestinationTests These test suites both make extensive use of the xUnit "Theory" attribute which involves the writing out of test parameters into the test name. I guess is that the the xUnit -> jUnit converter is failing to parse test names correctly if they contain the " marker in them. Environment: v1.5.3 XUnit Plugin Fix Versions: current Project: Jenkins Labels: plugin Priority: Minor Reporter: Ben Vaughan 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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
Gregory Boissinot commented on JENKINS-17520 xUnit check for old tests is too short At the moment, the plugin expects that the last modified date of test results were updated at build time (created by the plugin or the touch command is applied for example). The plugin tests that the test reports last modified date is inferior to 3 s. What is your build time? Moreover, you are able to check an option in the configuration to not activate this check. 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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
Gregory Boissinot started work on JENKINS-17520 xUnit check for old tests is too short Change By: Gregory Boissinot (08/Apr/13 8:59 PM) Status: Open In Progress 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] [bazaar] (JENKINS-13478) Redmine repository browser support should work in Bazaar and Mercurial
Alexandre Garnier closed JENKINS-13478 as Duplicate Redmine repository browser support should work in Bazaar and Mercurial Change By: Alexandre Garnier (08/Apr/13 8:40 PM) Status: Open Closed Resolution: Duplicate 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] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier commented on JENKINS-17376 BZR Environment Variables A possible solution : bazaar-plugin@JENKINS-17376 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] [nested-view] (JENKINS-17524) NPE when renaming job in My Views
David Ishee created JENKINS-17524 NPE when renaming job in My Views Issue Type: Bug Assignee: Unassigned Components: nested-view Created: 08/Apr/13 8:14 PM Description: I have the Nested View plugin installed. I was working in a nested view under my personal "My Views" tab. I renamed a job and got the following exception. The job does get renamed, but it disappears from the View it was in. I have to manually add it back to the view. It doesn't seem to do this on normal views outside "My Views". Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier commented on JENKINS-17376 BZR Environment Variables Does it make sense to add these variables? A build does not necessarily build only one commit and then there are multiple committers and messages. It is possible to do it, but is the last or first commit the more relevant? The solution I think of would not populate these variables in case of build without new commit (launched by a user or other build). 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Gregory Boissinot resolved JENKINS-17438 as Fixed xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Change By: Gregory Boissinot (08/Apr/13 7:58 PM) Status: Open Resolved Resolution: 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
SCM/JIRA link daemon commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/6f0d4a8a6445ac66a07325acc3e778f895e4b576 Log: Merge pull request #4 from bobtheshrew/patch-1 Fix for JENKINS-17438 Compare: https://github.com/jenkinsci/xunit-plugin/compare/9bfb2611775b...6f0d4a8a6445 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
SCM/JIRA link daemon commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Code changed in jenkins User: bobtheshrew Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/a7352df6dfb5b7e418fc2ea258c0ef1e6b67f689 Log: Fix for JENKINS-17438 Updated getXUnitToolInfoObject() to include: * BuildListener parameter * Use Util.replaceMacro() to expand CustomXSL string Updated performTests() call to getXUnitToolInfoObject() to include BuildListener parameter * Searched rest of the code, this seems to be the only call of getXUnitToolInfoObject() Addresses Bug: https://issues.jenkins-ci.org/browse/JENKINS-17438 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Erik Purins commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We still get this from time to time with debian squeeze master 1.504 jenkins, osx 10.8 client. It would be nice to resolve this, or at least handle this common error, with less stack trace, more human-readable text. Alternately, it would be nice if we could have a more fault-tolerant delete temporary file command, that either retries or schedules a cleanup of the temp file when it can. 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] [other] (JENKINS-1948) intermittent: fails to remove temporary file on remote.
Erik Purins commented on JENKINS-1948 intermittent: fails to remove temporary file on remote. This is still occurring 1.504 debian squeeze master, osx 10.8 slave. If it's related to an unreliable connection and is this frequent, maybe a better error message (instead of the entire remote action callstack) or more fault-tolerent remote action retry system could be implemented? 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like 'latestfailedbuild' unfortently the fix I have done is not working on all supported OS and also I have to search for some compatibility mode to older jenkins versions than 1.507. therfore it takes a little bit longer to fix this problem. stay tuned I'm working on it... 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] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier updated JENKINS-17376 BZR Environment Variables Change By: Alexandre Garnier (08/Apr/13 7:35 PM) Description: When a Jenkins job executes, it sets some environment variables. It would be nice if BZR variables were available. I saw that BZR_REV--NO-+ID+ and BZR_REVISION are available, but it doesn't look like they currently work.I would also like to requestBZR_AUTHOR or BZR_COMMITER BZR_COMMITTER BZR_MESSAGEWould these be possible to implement? 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] [parameterized-trigger] (JENKINS-17523) Gradle build parameter are not supplied correctly - Parameterized-trigger plugin
Jérémie Charest
created JENKINS-17523
Gradle build parameter are not supplied correctly - Parameterized-trigger plugin
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
08/Apr/13 7:24 PM
Description:
When using the "trigger other jobs" feature, build parameters are not send correctly to Gradle jobs.
The plugin format arguments by adding a -Dxxx which is an Ant syntax. In Gradle, build arguments follow -Pxxx syntax.
Example :
Predefined parameters : release=${release}
Job call (console output) : \gradle -Drelease=true
Should be : \gradle -Prelease=true
Environment:
Windows Server 2008 R2
parameterized-trigger v2.17
Jenkins v1.486
Project:
Jenkins
Labels:
plugin
gradle
Priority:
Minor
Reporter:
Jérémie Charest
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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi Fred. I'll cut a new release with this fix included tomorrow, but it takes a few hours for the backend infrastructure to update the Jenkins update site. Let me know if you need anything in the meantime. Thanks! Bruno 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] [android-emulator] (JENKINS-17522) Ability to start emulator only if Android build succeeds
Austyn Mahoney created JENKINS-17522 Ability to start emulator only if Android build succeeds Issue Type: New Feature Assignee: Christopher Orr Components: android-emulator Created: 08/Apr/13 7:21 PM Description: Waiting for the emulator to start should not be a requirement for an Ant build to start. On a server where you are forced to use the ARM emulator, it can be up to 3-5 minutes before your build even starts. The build can then fail, rendering the emulator useless for this particular build, and wasting 3-5 minutes of build time. Project: Jenkins Priority: Major Reporter: Austyn Mahoney 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita edited a comment on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hello @Supratim, Sorry for the delay. I've been busy with other project/plug-ins and couldn't find a cycle to work on Jenkins, TestLink or on this plug-in. Sorry. Since last Wednesday I've been working on these tools, but first I had to release a 1.9.4 testlink-java-api version. Yesterday I released another version of the testlink-java-api, 1.9.5-0. Now I'm working on these issues for 1.9.5/1.9.6. Thanks for confirming this issue @Fred. I'll take a look on this. Looks like a simple mismatch between the parameters of the testlink-java-api used by the plug-in, and TestLink. BTW, let me say that today I'm extremely happy, to receive a comment in this plug-in by you. When I wrote this plug-in, the initial version, was highly influenced by your blog entries. I was working on a telecom company, as QA engineer for the first time, and faced the need to integrate my CI jobs with the Test Management team. Not knowing much about test management, your blog was one of the most important resources. So, thank you very much!!! 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] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.
Michael Marcil updated JENKINS-17521 javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. Change By: Michael Marcil (08/Apr/13 7:14 PM) Description: I have a .NET DLL which contains tests that run with NUnit 2.5When a crash happens, the XML is malformed and the plugin crashes.I know the test should be fixed, but would it be possible for the plugin to not crash or filter the XML so that the failing test displays a generic error message in the final report.There's the call stack :--hudson.util.IOException2: remote file operation failed: *** at hudson.remoting.Channel@* at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237)Caused by: hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:57) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source)Caused by: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:67) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55) ... 12 moreCaused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source) ... 16 moreCaused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) ... 17 more--Part of the failing test output that is obviously causing the error :ydü> H† cÔ @?ˆ Ô¯ @v& @v& ? '?«C-äD|ªÔ¯ '?¶xŠï?;Ï’<Òš“÷[ ·ƒk>' ?…Ï <…6¤Ö c?…Ï ?…Ï @v& Ô¯ ?ÔÏ X…6 cäD?T`…6�& c\…6 >' Ô¯ |…6¤Ö cÔ¯ Ô¯ @v& _c"m,) co…6Ô¯ @†' �ƒ6ÞR‰ Ts? 6 …â� ·…6œb"mD®< 6Ñ…6BMO 69?O 6ÿ ‰ ÞR‰ Q?O ÿ ‰ 8†6@ › 6„1? › 6$ 6 „„6 2? @185** Thanks Thank you This message is automatically generated by JIRA.
[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.
Michael Marcil created JENKINS-17521 javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. Issue Type: Bug Affects Versions: current Assignee: redsolo Components: nunit Created: 08/Apr/13 7:13 PM Description: I have a .NET DLL which contains tests that run with NUnit 2.5 When a crash happens, the XML is malformed and the plugin crashes. I know the test should be fixed, but would it be possible for the plugin to not crash or filter the XML so that the failing test displays a generic error message in the final report. There's the call stack : -- hudson.util.IOException2: remote file operation failed: *** at hudson.remoting.Channel@* at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:57) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Caused by: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:67) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55) ... 12 more Caused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source) ... 16 more Caused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) ... 17 more -- Part of the failing test output that is obviously causing the error : ydü> H† cÔ@?ˆ Ô¯ @v& @v& ? '?«C-äD|ªÔ¯ '?¶xŠï?;Ï’<Òš“÷[·ƒk>' ?…Ï <…6¤Ö c?…Ï ?…Ï @v& Ô¯ ?ÔÏ X…6 cäD?T`…6�& c\…6 >' Ô¯ |…6¤Ö cÔ¯ Ô¯ @v& _c"m,) co…6Ô¯ @†' �ƒ6ÞR‰Ts?
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Fred Beringer commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hey Bruno, thanks for the quick fix! Need to find some time to test it this week. Happy to have influenced you one way or another But you're doing the real work here for the software testing community, so thanks for this! Fred 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] [disk-usage] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund assigned JENKINS-17508 to Kohsuke Kawaguchi The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503. Change By: Per J. Lund (08/Apr/13 7:07 PM) Assignee: vjuranek Kohsuke Kawaguchi 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] [disk-usage] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund
commented on JENKINS-17508
The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
I have investigated this problem further and found the following:
I have added some log to the LogRotator.java in both 1.502 and 1.510 - in the 'perform' method:
Added print-out of artifactsDir in the loop below:
if(artifactNumToKeep!=null && artifactNumToKeep!=-1) {
List> builds = job.getBuilds();
for (Run r : copy(builds.subList(Math.min(builds.size(), artifactNumToKeep), builds.size( {
LOGGER.log(INFO, "artifactsDir = {0} ", r.getArtifactsDir());
The log seen in version 1.502 is e.g:
INFO: artifactsDir = /var/lib/jenkins/jobs/PJLTEST/modules/com.corena.core$repository-management/builds/2013-04-08_20-28-13/archive
while in 1.510 it is e.g.:
INFO: artifactsDir = /var/lib/jenkins/jobs/PJLTEST/builds/2013-04-08_20-29-49/archive
This shows that it is a completely different behaviour between the two version and now artifacts will be removed as the directory seen in 1.510 does not even exist.
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] [xunit] (JENKINS-17520) xUnit check for old tests is too short
jpschewe created JENKINS-17520 xUnit check for old tests is too short Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 08/Apr/13 6:50 PM Description: The test for old test results is a little short. 4.1 seconds doesn't seem too old to me. 13:41:34 [xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run? 13:41:34 * /nfshomes/hudson/.hudson/jobs/grex-bps-geodesy/workspace/bps/geodesy-cpp/build/test/cpptestresults.xml is 4.1 sec old 13:41:34 Project: Jenkins Priority: Trivial Reporter: jpschewe 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] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn commented on JENKINS-17431 500 Internal Server Error on attempt to run a build thank you for responding. i see it has been changed to major from blocker... i think it should be blocker, as this problem prevents build to run... and our build engineer after we got this 500 response, ran build manually with mvn command... and build was fine. so, this tells me, that there is nothing wrong with the code, nor with subversion. and, please, let me make my point clearer. I saw the plugin code - it is very interesting and neat... however, I think in order to make a decision whether or not to run the build - you don't need to obtain the time and run svn command to see if there is any difference in the code between timestamps. 1. the difference can be found in easier way. svn -r is one of them. 2. the timestamp itself... is never reliable thing, in my opinion. there so many things affecting it, so you simply cannot rely on it. name just a few, would be: the precision you are retriving timestamp and other computer is different. the time between machines is NEVER the same. even ntpd server is synchronizing it, however, it runs periodically, plus, if nptd finds significant difference, it won't adjust time fully, being afraid to break system dependant thing, so will do it gracefuly... while your program obtains time... i can list some other things affecting timestamp... if you want to... so, my main point is do not use timestamp to calculate difference. i think would be easier and faster to calculate size of checked out space before svn update and after. ...and I am not saying that svn response on it is completely valid... 500 error actually perhaps not the best answer... but this is just a matter of how developer typed in the text in response to the error. and according to what I see in subversion code, and how I understand it - subversion could not find such timestamp in its db, so... responded... why it could not find it? could be because this time doesn't exist yet (like i said... time on the machine sending the request is running a little bit ahead of svn server), or it is being malformed somehow, or it is something else... it is not easy to process timestamps... anyway, please see below the errors: ERROR: Failed to update https://svn.xxx.com:xxx/svn/XXX org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/x/!XXX/default': 500 Internal Server Error (https://.com:xxx) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:207) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:475) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:464) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:486) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:143) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth closed JENKINS-17519 as Not A Defect After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online After much messing around, downgrading to SSH Plug-in to 0.22 and reverting to Jenkins 1.508 and then upgrading to 1.510 and then upgrading the plug-in separately. I have managed to get it working with a user and password defined in the credentials plugin. Change By: Steve Haworth (08/Apr/13 6:31 PM) Status: Open Closed Resolution: Not A Defect 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] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita resolved JENKINS-17442 as Fixed When connecting to TestLink, finding error ClassCastException Change By: Bruno P. Kinoshita (08/Apr/13 6:28 PM) Status: Open Resolved Resolution: 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] [core] (JENKINS-17422) Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter
Bruno P. Kinoshita commented on JENKINS-17422 Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter Hi, I used the wrong bug id in the commit log. Please ignore the message above. Sorry for the noise. /Bruno 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] [core] (JENKINS-14749) Errors in style.css
Pedro Rodriguez updated JENKINS-14749 Errors in style.css Change By: Pedro Rodriguez (08/Apr/13 5:40 PM) Assignee: Pedro Rodriguez 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] [core] (JENKINS-14749) Errors in style.css
Pedro Rodriguez assigned JENKINS-14749 to Pedro Rodriguez Errors in style.css Change By: Pedro Rodriguez (08/Apr/13 5:38 PM) Assignee: Pedro Rodriguez 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Note: Even rolling back the Windows VM to Jenkins v1.508 the nodes remain offline. 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth created JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 08/Apr/13 5:31 PM Description: Slave nodes fail to start, Error Log shows, [04/08/13 18:22:49] [SSH] Opening SSH connection to :22. [04/08/13 18:22:53] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:462) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) [04/08/13 18:22:53] [SSH] Connection closed. Environment: Master is a Windows 64 Bit VM with 6 Linux slave Nodes Project: Jenkins Labels: ssh Priority: Blocker Reporter: Steve Haworth 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
dogfood commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Integrated in jenkins_main_trunk #2445 Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." (Revision 73bf0e5b4f1c038101e284ee8adfb56b0760addc) Result = SUCCESS Jesse Glick : 73bf0e5b4f1c038101e284ee8adfb56b0760addc Files : changelog.html core/src/main/java/hudson/model/Label.java 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
dogfood commented on JENKINS-8614 ProcessTreeTest fails on Windows Integrated in jenkins_main_trunk #2444 Fixed JENKINS-8614 ProcessTreeTest fails on Windows (Revision 97c28e0a516a1647c3621838fb0629368c7b5873) [Fixed JENKINS-8614] ProcessTreeTest fails on Windows (Revision 4709490334c2affd6b82270449daff7a6cb1e5e1) fixed JENKINS-8614 ProcessTreeTest fails on Windows (Revision cdc18ec56987204535c9919ea385c555d3d66863) Result = SUCCESS wang_limin : 97c28e0a516a1647c3621838fb0629368c7b5873 Files : core/src/main/java/hudson/util/ProcessTree.java wang_limin : 4709490334c2affd6b82270449daff7a6cb1e5e1 Files : core/src/main/java/hudson/util/ProcessTree.java wang_limin : cdc18ec56987204535c9919ea385c555d3d66863 Files : core/src/main/java/hudson/util/ProcessTree.java 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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Justin Ryan
commented on JENKINS-17513
For SVN only one workspaceupdater is supported
Please provide a full example of DSL code, and possibly the XML of what you're trying to accomplish in the future.
NodeEnhancement, in the context of a div ("/") will try to match an element by name and attributes. In your case, you'll have to leave off the class attribute and then override it. E.g.
def updaterNode = scmNode / workpaceUpdater
updateNode.attributes().put('class','hudson.scm.subversion.UpdateWithRevertUpdater')
It's definitely not ideal, but that should work for you.
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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Justin Ryan started work on JENKINS-17513 For SVN only one workspaceupdater is supported Change By: Justin Ryan (08/Apr/13 3:49 PM) Status: Open In Progress 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Jesse Glick commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Well probably we just do not want to display a MavenModule here under any conditions, since (AFAIK) it is not possible to tie an individual module to a label, only to a module set. 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Marc Günther commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Isn't the problem that getAssignedLabel() of a MavenModule returns the last slave that the parent was build on (contrary to my observation above, which must have been mistaken)? 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] [subversion] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
kutzi commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history And it's easily reproducable by using $Id:$ as SVN keywords? 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] [publish-over-ftp] (JENKINS-17165) "Publish over FTP" plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Alexander Fischer commented on JENKINS-17165 "Publish over FTP" plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504 I updated from Jenkins 1.497 to Jenkins 1.510. Now the only not working plugin is the "Publish over FTP"-plugin. The configuration is lost after restart of Jenkins. How can we speedup the Bugfixing? Do you need some more support? 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] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
Michael Chmielewski created JENKINS-17518 When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: extended-choice-parameter Created: 08/Apr/13 3:18 PM Description: Currently the multiselect choice parameter delimits multiple selections with a comma. I have a situation where I am trying to create a staging/release package from multiple archived builds for use in an automated deployment system. I would like to use the multiselect choice parameter to select locations that the packages are going to be deployed to, and create a path structure with that information. As I do not want to necessarily create deeply nested folders, it would be nice to either declare the delimiter myself or choose from a small set of directory name safe characters (windows or linux). I think the comma delimiter should clearly be the default behavior. Environment: CentOS 6.3 Linux Project: Jenkins Priority: Major Reporter: Michael Chmielewski 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] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)
Andrew Zellman updated JENKINS-17517 Support for dynamic skins (a la JellyBean devices) Change By: Andrew Zellman (08/Apr/13 3:13 PM) Description: The Android Emulator plug-in does not expose the ability to use a dynamic skin.The problem is that newer devices do not have hardware buttons for most functionality (Home, Menu, etc.). Instead, they use a dynamic skin. This is especially true in devices running JellyBean. However, when using the Android Emulator plug-in, I have not been able to generate this type of device image.For instance, when I create an emulator using Android Virtual Device Manager, I can create it from a Device Definition. If I choose Nexus 7 by Google, I get an option to "Display a skin with hardware controls" under the "Skin:" category. This does not appear to be exposed in the Android Emulator plug-in.Upon inspection of the config.ini files in the AVD created through the GUI and the AVD created by Jenkins, I noticed the presence of skin.dynamic=yes. However, when I tried adding that as a Hardware property, I was unable to view the dynamic skin. The reason that this is a blocker for me is that I'm trying to run tests that rely on the existence of a MENU button, and I'm unable to hit that button if it does not exist. 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
SCM/JIRA link daemon commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Label.java http://jenkins-ci.org/commit/jenkins/73bf0e5b4f1c038101e284ee8adfb56b0760addc Log: Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." This reverts commit 3a6de84f6746d54dd0f3048312db067c835ee727. (Regressed JENKINS-15666.) Conflicts: changelog.html 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] [core] (JENKINS-15666) Label.getTiedJobs ignores non-top-level jobs
SCM/JIRA link daemon commented on JENKINS-15666 Label.getTiedJobs ignores non-top-level jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Label.java http://jenkins-ci.org/commit/jenkins/73bf0e5b4f1c038101e284ee8adfb56b0760addc Log: Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." This reverts commit 3a6de84f6746d54dd0f3048312db067c835ee727. (Regressed JENKINS-15666.) Conflicts: changelog.html 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon resolved JENKINS-8614 as Fixed ProcessTreeTest fails on Windows Change By: SCM/JIRA link daemon (08/Apr/13 3:01 PM) Status: In Progress Resolved Resolution: 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: limin wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/cdc18ec56987204535c9919ea385c555d3d66863 Log: fixed JENKINS-8614 ProcessTreeTest fails on Windows 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: limin wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/4709490334c2affd6b82270449daff7a6cb1e5e1 Log: [Fixed JENKINS-8614] ProcessTreeTest fails on Windows Add exception handler for getEnvironmentVariables(). 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/91000fa5699c5fc7b48fcb061be9ded980aa8639 Log: Merge pull request #752 from lmwang/master [FIXED JENKINS-8614] ProcessTreeTest fails on Windows Compare: https://github.com/jenkinsci/jenkins/compare/b99a794c6ed2...91000fa5699c 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] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: Limin Wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/97c28e0a516a1647c3621838fb0629368c7b5873 Log: Fixed JENKINS-8614 ProcessTreeTest fails on Windows 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Jesse Glick reopened JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs This breaks JENKINS-15666; it was intentional to show items in folders. Change By: Jesse Glick (08/Apr/13 2:56 PM) Resolution: Fixed Status: Resolved Reopened 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] [android-emulator] (JENKINS-16407) Android Emulator plugin does not compile with Java 7
Christopher Orr resolved JENKINS-16407 as Fixed Android Emulator plugin does not compile with Java 7 I moved the Jenkins dependency to 1.466 and now the plugin builds with Java 7. Change By: Christopher Orr (08/Apr/13 2:52 PM) Status: Open Resolved Resolution: 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] [core] (JENKINS-12032) Include SCM changes in environment variables
Christopher Orr commented on JENKINS-12032 Include SCM changes in environment variables For info, there's a workaround in this StackOverflow answer: http://stackoverflow.com/a/11837662/234938 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: src/main/java/hudson/plugins/mercurial/MercurialStatus.java http://jenkins-ci.org/commit/mercurial-plugin/0a71d81d3d205d24d3c3065ca7f693d4ea0e4b16 Log: JENKINS-17409 looselyMatches does not need to check for repository==null 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialStatus.java src/test/java/hudson/plugins/mercurial/MercurialStatusTest.java http://jenkins-ci.org/commit/mercurial-plugin/138dd817eea8020f3c0dddcbc21fba02799a1478 Log: [FIXED JENKINS-17409] remove extraneous dependency, slightly better flow 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialStatus.java http://jenkins-ci.org/commit/mercurial-plugin/b0abcf4403036bd1be3340469e2d29b2b9985790 Log: Merge pull request #35 from jerrymaloney/master [FIXED JENKINS-17409] looselyMatches throws exception if second parameter (repository) is null Compare: https://github.com/jenkinsci/mercurial-plugin/compare/36f762600f08...b0abcf440303 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon resolved JENKINS-17409 as Fixed looselyMatches throws exception if second parameter (repository) is null Change By: SCM/JIRA link daemon (08/Apr/13 2:41 PM) Status: In Progress Resolved Resolution: 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialStatus.java src/test/java/hudson/plugins/mercurial/MercurialStatusTest.java http://jenkins-ci.org/commit/mercurial-plugin/c12bfbfd24eb53760764a20a35558ef7bfcadd29 Log: [FIXED JENKINS-17409] unhandled exception in looselyMatches 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] [security] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Jesse Glick
updated JENKINS-17510
Create an executor service wrapper class that sets the security context in each thread
Change By:
Jesse Glick
(08/Apr/13 2:24 PM)
Description:
Initially suggested by jglick when I asked a question on the developer group https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/H8gAZcDOqgc -Creates a delegating
{{
ExecutorService
}}
implementation whose submit and related methods capture the current
{{
SecurityContext
}}
and then wrap the task in a block that resets the context afterwards. Using this one could simply write:
{code}
SomeUtilityClass.wrapExecutorWithSecurity(service).submit(new Callable() { public Void call() throws Exception { Jenkins.getInstance().getItem(whatever); // should work return null; } });
{code}
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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Linards L edited a comment on JENKINS-17248 java.lang.NullPointerException by start Any other plugin affected? I am prepping to upgrade from 1.494 to 1.510 this weekend ... but seems like this and this (https://issues.jenkins-ci.org/browse/JENKINS-17514) is party-stopper ... 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] [nested-view] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Martin Kutter reopened JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated The issue is not fixed in Jenkins 1.467. I'm on 1.480.3-LTS with Role Strategy plugin 1.1.2 and Nested View Plugin 1.8. We have several top-level-views, which are only shown, when a user has the (global) View.READ permission. They are not shown as tabs in the UI, but can be accesed by directly invoking the view's URL. These views are of the type "Nested View" and do not contain other jobs. This means that the "backward compatibility" trick in JENKINS-3681 does not work, when a view contains only other views (and no jobs). A user can either see all views (by means of the View.READ) permission, or only views containing Jobs. Change By: Martin Kutter (08/Apr/13 1:52 PM) Resolution: Duplicate Status: Closed Reopened 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] [core] (JENKINS-17516) "script textarea" quite annoying on Safari
Marc Günther created JENKINS-17516 "script textarea" quite annoying on Safari Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/13 1:51 PM Description: The "script textarea" (the one with the line numbers, as for example used in the Script Console and the scriptler plugin) has several annoying quirks (at least on Safari, didn't try on other browsers): doubleclick 'n drag to select multiple words does not work tripleclick 'n drag to select multiple lines does not work it insists on autoindenting lines by 2 characters, when you press return, even if it makes no sense at all it jumps around on every key press and mouse click (making it impossible to use the mouse at all), when you have a long line somewhere in the file, that is not currently visible. It is usually easier to copy the text into an external editor, and paste it back after editing, than using this control. Environment: Safari 6.0.3, MacOSX 10.8.3 Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [hp-application-automation-tools-plugin] (JENKINS-17515) HP Security Vulnerability in Password Handling
David Ehringer created JENKINS-17515 HP Security Vulnerability in Password Handling Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 08/Apr/13 1:26 PM Description: https://github.com/jenkinsci/hp-application-automation-tools-plugin/blob/master/src/main/java/com/hp/application/automation/tools/EncryptionUtils.java uses a non-secret key (the key is published on GitHub) and a static initialization vector. This renders the encryption useless. Furthermore, the exposed password is written to a text file in the build filesystem, which can be viewed directly through the Jenkins UI via file archiving. Project: Jenkins Priority: Blocker Reporter: David Ehringer 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] [core] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Ilya Lebedev created JENKINS-17514 NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510 Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/13 1:15 PM Description: java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@233c779c[cserver-CONS-at1-job] project.getModules()=[hudson.maven.MavenModule@15e87941[cserver-CONS-at1-job/com.ctrader:xt-acceptance-tests][cserver-CONS-at1-job/com.ctrader:xt-acceptance-tests][relativePath:AcceptanceTests], hudson.maven.MavenModule@6aa0d4a3[cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][relativePath:AcceptanceTests]] project.getRootModule()=hudson.maven.MavenModule@6aa0d4a3[cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][relativePath:AcceptanceTests] FATAL: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: One master node and three slave node. All are running CentOS release 5.9 inside VM. Project: Jenkins Priority: Major Reporter: Ilya Lebedev 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-iss
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Linards L commented on JENKINS-17248 java.lang.NullPointerException by start Any other plugin affected? I am prepping to upgrade from 1.494 to 1.510 this weekend ... 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.
