[JIRA] [core] (JENKINS-17942) Break words in prolonged strings
dogfood commented on JENKINS-17942 Break words in prolonged strings Integrated in jenkins_main_trunk #2720 JENKINS-17942 Break long values in property tables (Revision 9d2b204ca1ab90d1a1102136aba13e4cd0146947) Result = UNSTABLE ogondza : 9d2b204ca1ab90d1a1102136aba13e4cd0146947 Files : core/src/main/resources/lib/hudson/propertyTable.jelly 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-10184) wrong timestamps in build timeline
dogfood commented on JENKINS-10184 wrong timestamps in build timeline Integrated in jenkins_main_trunk #2720 FIXED JENKINS-10184 wrong timestamps in build timeline - added (Revision f6ac62bfba80093b9cf3957b5055fcce2a15002a) Result = UNSTABLE Fred G : f6ac62bfba80093b9cf3957b5055fcce2a15002a Files : core/src/main/resources/hudson/model/BuildTimelineWidget/control.jelly 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] [cli] (JENKINS-18282) Support node manipulation via Jenkins CLI
dogfood commented on JENKINS-18282 Support node manipulation via Jenkins CLI Integrated in jenkins_main_trunk #2720 JENKINS-18282 Introduce get-node CLI command (Revision 548e9b8bbf7910227e416417d498a505cd847d96) JENKINS-18282 Introduce update-node CLI command (Revision 92a74104af026362962ccd8121c0e1d1f755b184) JENKINS-18282 Introduce create-node CLI command (Revision df786136bd74b233f8d32b9894f27db84e9b803b) FIXED JENKINS-18282 Optionally override name from XML in create-node CLI command (Revision 7ac7967f55d11e43402e12c5c98a6bc83fa838b4) Result = UNSTABLE ogondza : 548e9b8bbf7910227e416417d498a505cd847d96 Files : core/src/main/java/hudson/cli/GetNodeCommand.java core/src/main/java/hudson/cli/handlers/NodeOptionHandler.java test/src/test/java/hudson/cli/GetNodeCommandTest.java core/src/main/resources/hudson/cli/Messages.properties ogondza : 92a74104af026362962ccd8121c0e1d1f755b184 Files : core/src/main/java/hudson/model/Computer.java test/src/test/resources/hudson/cli/node.xml core/src/main/java/hudson/cli/UpdateNodeCommand.java core/src/main/resources/hudson/cli/Messages.properties test/src/test/java/hudson/cli/UpdateNodeCommandTest.java ogondza : df786136bd74b233f8d32b9894f27db84e9b803b Files : core/src/main/resources/hudson/cli/Messages.properties core/src/main/java/hudson/cli/CreateNodeCommand.java test/src/test/java/hudson/cli/CreateNodeCommandTest.java ogondza : 7ac7967f55d11e43402e12c5c98a6bc83fa838b4 Files : test/src/test/java/hudson/cli/CreateNodeCommandTest.java core/src/main/java/hudson/cli/CreateNodeCommand.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] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project What I am trying to do is fairly simple. I have a Jenkins job that builds a maven project using the maven goals "clean deploy". As part of these goals the unit tests are being run and reported by Jenkins (and/or RTC now that you have added the RTC build support). What I wanted to do with the multi-configuration project is run the maven project with the goals "clean test" but with different JDK's as we have seen some problems moving between JDK6 and JDK 7. Hence I created several JDK's in my Jenkins configuration and then I created a multi-configuration project and selected my different JDK's. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18787) Project inheritance support
Alex Al created JENKINS-18787 Project inheritance support Issue Type: Improvement Assignee: Unassigned Components: core Created: 17/Jul/13 7:28 AM Description: Is it possible to make native project inheritance support in Jenkins? I haven't found any decent plugin to overcome the issue. I have a lot of similar projects in Jenkins. I want to have several different configurations for some of these projects. Yes, I can copy each project so that I don't need configure it from scratch. But if I want make change in all of them (since they are identical), it becomes disaster. I need to go to each of 40 projects and make similar small change in each. Phhh, so annoying. Similar question on SO: http://stackoverflow.com/q/6541165/1002036 Project: Jenkins Priority: Major Reporter: Alex Al 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
thetaphi commented on JENKINS-18667 NullPointerException when saving job config My job is not a matrix one, but still fails! In my case, the node where the job is running is offline (only starts when job runs), so the root dir is obviously null, because node is 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] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
sogabe commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) @Shannon, Did you install JQuery plugin? 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-18641) People View does Not Populate (makeStaplerProxy)
sogabe edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) @Shannon, Did you install JQuery plugin? Jenkins #A with JQuery Plugin - reproduced Jenkins #B without Jquery plugin - not reproduced 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] [dos-trigger] (JENKINS-18788) DOS Trigger plugin does not support maven projects
Mikhail Tsaplin created JENKINS-18788 DOS Trigger plugin does not support maven projects Issue Type: Bug Assignee: Unassigned Components: dos-trigger Created: 17/Jul/13 8:11 AM Description: Please check stacktrace Jul 17, 2013 11:05:38 AM hudson.triggers.Trigger checkTriggers WARNING: org.jenkinsci.plugins.dostrigger.DosTrigger.run() failed for SON java.lang.ClassCastException: hudson.maven.MavenModuleSet cannot be cast to hudson.model.Project at org.jenkinsci.plugins.dostrigger.DosTrigger.run(DosTrigger.java:80) at hudson.triggers.Trigger.checkTriggers(Trigger.java:261) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:209) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source) Project: Jenkins Priority: Major Reporter: Mikhail Tsaplin 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] [build-pipeline] (JENKINS-18789) Search/Filter Capability?
Ralph Bolton created JENKINS-18789 Search/Filter Capability? Issue Type: Improvement Assignee: Unassigned Components: build-pipeline Created: 17/Jul/13 8:18 AM Description: We're starting to use the build-pipeline plugin fairly extensively, and are finding that it can be hard to find your particular project in a list of many others. In our world, each commit creates a new pipeline, and so a new row in the pipeline view. We've got a few dozen different projects pipelined, all of which progress through our environments at different speeds. That means it's quite likely that a slow project might make it through a couple of pipeline steps but "drop off the bottom of the page" before it makes it all the way to the end of the pipeline. Would it be possible to add a search or filter capability, such that you could type in the name of a project and just be shown the pipelines for it? That way, whilst there might be lots of rows for your project, at least you'd be able to see the one that got part-way through the pipeline and then push it a little further up. If there's any way I can help to implement this suggestion, please let me know. Project: Jenkins Priority: Minor Reporter: Ralph Bolton 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] [ivy] (JENKINS-18790) Ivy job type should support fingerprinting of consumed dependencies
stephenconnolly created JENKINS-18790 Ivy job type should support fingerprinting of consumed dependencies Issue Type: Bug Assignee: Timothy Bingaman Components: ivy Created: 17/Jul/13 8:58 AM Description: While the Ivy job type identifies upstream and downstream Job relationships, it does not currently provide full support for Jenkins's way to identify Build relationships... namely fingerprinting. The Ivy job type allows one to fingerprint things that have been created by the build, but if the dependencies are not copied into the build workspace there is no way for the user to configure the standard Jenkins fingerprinter to capture the fingerprints that were resolved by the project but used while remaining in the Ivy cache. This means that other plugins that rely on fingerprint information to establish a chain of cause and effect between specific builds of specific projects are unable to reliably do so. To correctly support this with the Ivy job type it would need to do the following: Capture the fingerprints of all dependencies resolved by the build (those fingerprints indicate upstream dependencies) Project: Jenkins Priority: Minor Reporter: stephenconnolly 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] [naginator] (JENKINS-18792) Time units should be displayed for the scheduling delay
Paul Croome created JENKINS-18792 Time units should be displayed for the scheduling delay Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator Created: 17/Jul/13 9:08 AM Description: In the Nagination configuration, there is a field 'Delay before schedule' Fixed delay' nnn. It would be very nice if the time units were displayed. I believe the units are minutes. A possible solution: Delay before schedule Fixed delay nnn minutes Project: Jenkins Priority: Minor Reporter: Paul Croome 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] [crowd2] (JENKINS-18791) session.validationinterval is not saved
Thomas S. created JENKINS-18791 session.validationinterval is not saved Issue Type: Bug Affects Versions: current Assignee: Thorsten Heit Components: crowd2 Created: 17/Jul/13 9:07 AM Description: Hello there, when changing the validationinterval from 2 to another value (20160) it is not saved. The next time the page is opened, the validationinterval is again 2. The jenkins-log is correct: Jul 17, 2013 10:48:09 AM com.atlassian.crowd.service.client.ClientPropertiesImpl loadAndLogPropertyString INFO: Loading property: 'session.validationinterval' : '20160' Environment: Jenkins 1.509.2 Project: Jenkins Priority: Critical Reporter: Thomas S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [naginator] (JENKINS-18792) Time units should be displayed for the scheduling delay
Paul Croome updated JENKINS-18792 Time units should be displayed for the scheduling delay Change By: Paul Croome (17/Jul/13 9:14 AM) Description: Inthe Nagination Naginator configuration,thereisafieldDelaybeforescheduleFixeddelaynnn.Itwouldbeveryniceifthetimeunitsweredisplayed.Ibelievetheunitsareminutes.Apossiblesolution:DelaybeforescheduleFixeddelaynnnminutes 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-18405) Findbugs plugin unable to run on slaves with 1.519
James Howe commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 This is still cited as an issue in 521, 522 and 523 on the changelog. 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] [periodicbackup] (JENKINS-17487) Allow Excludes in Full Backup
Marc Brugger resolved JENKINS-17487 as Fixed Allow Excludes in Full Backup The pull request was merged today Change By: Marc Brugger (17/Jul/13 9:49 AM) 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] [periodicbackup] (JENKINS-17487) Allow Excludes in Full Backup
Marc Brugger assigned JENKINS-17487 to Marc Brugger Allow Excludes in Full Backup Change By: Marc Brugger (17/Jul/13 9:48 AM) Assignee: MarcBrugger 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-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Jose L Vazquez commented on JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 Thanks Tobias, That sounds like it would be the solution for me as well, but I have a couple of questions... 1- How do I know the PID of the slave task that Jenkins is running so that I could check its environment? 2- Where is the option 'Prefix Start Slave Command'? my Jenkins is in Spanish and I am having trouble finding that option. Is that a Jenkins general option or a per-project config attribute? I don't seem to find anything about configuring slaves on Jenkins. My config is a standalone one the web and the managed server is the same machine. Thanks again, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18686) Missing delete button for post build step
Rolf Geuenich commented on JENKINS-18686 Missing delete button for post build step This week I'm busy and the next two weeks I've got holidays. But after this I will try to disable plug ins and report the result. 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-18793) Jenkins LTS v. 1.509.2 blocker issue with Jenkins SSH Slaves plugin 0.27
Potroshitel Jack created JENKINS-18793 Jenkins LTS v. 1.509.2 blocker issue with Jenkins SSH Slaves plugin 0.27 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: plugin, ssh-slaves Created: 17/Jul/13 10:03 AM Description: I'm trying to connect to Jenkins Slave machines with SSH username and Certificate. No password. The public certificate on Jenkins slave resides in public certificate in /home/jenkins/.ssh/authorized_keys/id_rsa.pub. You can find the error below: 07/17/13 12:40:16 SSH Opening SSH connection to MY_HOSTNAME:22. ERROR: Server rejected the private key for jenkins (credentialId:b2bd2fe3-22e9-45dc-a7d1-/method:publickey) 07/17/13 12:40:17 SSH Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:954) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:488) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) 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) 07/17/13 12:40:17 SSH Connection closed. Due Date: 17/Jul/13 12:00 AM Environment: Jenkins Master: Windows 2008 x64 with Jenkins LTS v. 1.509.2, with private certificate in Jenkins directory Jenkins Slave: Centos 6.4 x64 with public certificate in /home/jenkins/.ssh/authorized_keys/id_rsa.pub Project: Jenkins Priority: Major Reporter: Potroshitel Jack 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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Richard Mortimer commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently This is related to the fix for JENKINS-11255. That change blocks makes the build queue rather than just block mid-build waiting for a port to become available. It is not clear to me from your report what problem this is causing you. Do the queued builds continue once the build holding the blocked port has completed? Is a build on one slave being blocked because a port is being used on another slave? Do you have a use case where you need all of the slaves to start running but then block during the build? I would help greatly if you could describe a simple test case that allows your problem to be reproduced/tested. 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-18719) Also show job name in list view configuration
Daniel Beck commented on JENKINS-18719 Also show job name in list view configuration It doesn't look like this is supported by /lib/form's checkbox. 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] [configurationslicing] (JENKINS-18794) Configuration slicing is failing with Maven 3.1.0
Julian Payne created JENKINS-18794 Configuration slicing is failing with Maven 3.1.0 Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 17/Jul/13 10:21 AM Description: The configuration slicing (1.37) in the latest version of Jenkins (1.523) is failing with Maven 3.1.0: Caused by: java.lang.NullPointerException at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getBuilders(MavenVersionSlicer.java:78) at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getValues(MavenVersionSlicer.java:56) at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getValues(MavenVersionSlicer.java:30) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:379) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) Due Date: 19/Jul/13 12:00 AM Project: Jenkins Labels: maven Priority: Major Reporter: Julian Payne 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-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Tobias Peters commented on JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 1) the pid should be easy to find, just by checking which java processes run on the node ps -aux | grep slave.jar should output something including a similar line jenkins 16699 0.1 11.9 1709700 245440 ? Sl Jul16 1:02 /usr/lib/jvm/sun-jdk-1.6/bin/java -jar slave.jar where as 2nd column (16699) is the pid 2) the config entry is found in the node configuration page launch method: "... via SSH..." Advanced "Prefix Start Slave Command", just beneath the "JVM Options" 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-5539) Extend Project-based Matrix Authorization Strategy with SCM Configuration option
Artur Szostak commented on JENKINS-5539 Extend Project-based Matrix Authorization Strategy with SCM Configuration option Any progress on a proper solution? 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-17757) IllegalStateException: Timer already cancelled from NodesCollector.scheduleCollectNow
SCM/JIRA link daemon commented on JENKINS-17757 IllegalStateException: Timer already cancelled from NodesCollector.scheduleCollectNow Code changed in jenkins User: evernat Path: src/main/java/org/jvnet/hudson/plugins/monitoring/NodesListener.java http://jenkins-ci.org/commit/monitoring-plugin/cb66c467903706df63ca07af21fc1fb5f50e1e66 Log: FIX JENKINS-17757 IllegalStateException: Timer already cancelled from NodesCollector.scheduleCollectNow 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-18793) Jenkins LTS v. 1.509.2 blocker issue with Jenkins SSH Slaves plugin 0.27
Potroshitel Jack commented on JENKINS-18793 Jenkins LTS v. 1.509.2 blocker issue with Jenkins SSH Slaves plugin 0.27 P.S. I want to mention that I have also tried to to connect to CentOS slave with username and password specified on master server - same error. I have also tried to put the private certificate directly into SSH Slave plugin - same error. I am able to connect from master to Centos slave through an SSH client. Also a couple of months ago I have used the old version of SSH Slaves plugin - and it was working fine. I haven't used the SSH plugin since then - and with the current version i'm having serious issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Jose L Vazquez commented on JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 Something is wrong here... ps aux |grep slave.jar never renders anything (and using the -aux instead makes my ubuntu box complain about ps syntax) It seems I don't have or use a slave.jar at all!?! Whereas using: ps aux |grep jenkins instead I get an extra process when a task is running on Jenkins (I guess that is the slave running): $ ps aux |grep jenkins jenkins924 0.3 14.9 1332708 617724 ? Ssl Jul09 35:15 /usr/bin/java -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -jar /usr/share/jenkins/jenkins.war --webroot=/var/run/jenkins/war --httpPort=7070 --prefix=/jenkins --ajp13Port=-1 --preferredClassLoader=java.net.URLClassLoader --logfile=/var/log/jenkins/jenkins.log jenkins 26158 119 0.9 1194144 40652 ? Sl 13:21 0:03 /usr/lib/jvm/java-6-sun/bin/java -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.3.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn /run/jenkins/war/WEB-INF/lib/remoting-2.24.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.3.jar 49861 Maybe I have a strange jenkins version? Mine is Jenkins ver. 1.519 When I do sudo cat /proc/slave_pid/environ I get something like: TERM=linuxJENKINS_HOME=/var/lib/jenkinsJAVA_HOME=/usr/lib/jvm/java-6-sunMAVEN_HOME=/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvnNODE_LABELS=masterXFILESEARCHPATH=/usr/dt/app-defaults/%L/DtUPSTART_JOB=jenkinsHUDSON_URL=http://rflabs.com/jenkins/JOB_URL=http://rflabs.com/jenkins/job/modcaja/PWD=/BUILD_ID=2013-07-17_13-18-44BUILD_TAG=jenkins-modcaja-274BUILD_URL=http://rflabs.com/jenkins/job/modcaja/274/NODE_NAME=masterNLSPATH=/usr/dt/lib/nls/msg/%L/%N.catBUILD_NUMBER=274LD_LIBRARY_PATH=/usr/lib/jvm/java-6-sun-1.6.0.45/jre/lib/i386/server:/usr/lib/jvm/java-6-sun-1.6.0.45/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.45/jre/../lib/i386UPSTART_EVENTS=runlevelEXECUTOR_NUMBER=1JENKINS_SERVER_COOKIE=69dd0d0208e62d55LANGUAGE=en_US.UTF-8BUILD_DISPLAY_NAME=#274WORKSPACE=/var/lib/jenkins/workspace/modcajaM2_HOME=/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvnPATH=/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn/bin:/usr/lib/jvm/java-6-sun/bin:/usr/lib/jvm/java-6-sun/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/binJENKINS_URL=http://rflabs.com/jenkins/LC_ALL=en_US.UTF-8RUNLEVEL=2PREVLEVEL=NHOME=/var/lib/jenkinsJOB_NAME=modcajaHUDSON_COOKIE=76876651-d2a6-4b47-9be6-47aedb62179aHUDSON_SERVER_COOKIE=69dd0d0208e62d55SVN_REVISION_1=1114SVN_REVISION=1114HUDSON_HOME=/var/lib/jenkinsSVN_URL=svn+ssh://svn.rflabs.com/data/subversion/modcaja/trunk/modcajaSVN_URL_1=svn+ssh://svn.rflabs.com/data/subversion/modcaja/trunk/modcajaLANG=en_US.UTF-8 In which every environment variable about locale seems to be correctly pointing to en_US.UTF-8 I can't find the "node configuration page" either, I guess I don't know how it was translated to Spanish or maybe I am using a different Jenkins version. Can I force my jenkins into English? how? 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-8606) ThinBackup only backs one job out of 10, and continually runs in the background
Ben Poole reopened JENKINS-8606 ThinBackup only backs one job out of 10, and continually runs in the background Hi Thomas, I'm still experiencing this issue with Jenkins 1.511 and ThinBackup 1.7.2 logs: == /var/log/jenkins/jenkins.log == Jul 17, 2013 12:42:02 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual INFO: Starting manual backup. Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup init INFO: No previous full backup found, thus creating one. Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 53 jobs to back up. Jul 17, 2013 12:42:03 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/lib/jenkins/backups'. java.io.FileNotFoundException: Source '/var/lib/jenkins/jobs/nationalvoices-INTEGRATION_LAMORAK/builds/lastUnstableBuild' does not exist at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:866) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:302) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:270) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:208) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:196) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:175) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:142) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Thread.java:722) I think the write privileges error is a red herring because jenkins does have the correct privs access to the dir. Cheers Ben Change By: Ben Poole (17/Jul/13 11:44 AM) 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] [thinBackup] (JENKINS-8606) ThinBackup only backs one job out of 10, and continually runs in the background
Ben Poole commented on JENKINS-8606 ThinBackup only backs one job out of 10, and continually runs in the background root@lamorak:/var/lib/jenkins/jobs/nationalvoices-INTEGRATION_LAMORAK/builds# ls -lh total 4.0K lrwxrwxrwx 1 root root 19 Jul 11 17:03 1 - 2013-07-11_17-03-59 drwxr-xr-x 2 root root 4.0K Jul 11 17:09 2013-07-11_17-03-59 lrwxrwxrwx 1 root root2 Jul 11 15:01 lastFailedBuild - -1 lrwxrwxrwx 1 root root1 Jul 11 17:09 lastStableBuild - 1 lrwxrwxrwx 1 root root1 Jul 11 17:09 lastSuccessfulBuild - 1 lrwxrwxrwx 1 root root2 Jul 11 15:01 lastUnstableBuild - -1 lrwxrwxrwx 1 root root2 Jul 11 15:01 lastUnsuccessfulBuild - -1 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] [timestamper] (JENKINS-18795) Timestamper sometimes does not update its timestamps
Dirk Kuypers created JENKINS-18795 Timestamper sometimes does not update its timestamps Issue Type: Bug Affects Versions: current Assignee: stevengbrown Components: timestamper Created: 17/Jul/13 11:50 AM Description: Sometimes I was puzzled by timestamps printed by timestamper being not correct, but could not proove it. Luckily now I can because of another program (SONAR) printing it's own time-stamps. 09:49:30 11:23:02.889 INFO - timeout Test RohdeSchwarz.Contest.PhysicalDevicesTests/SscuMimoTest05/SscuMimo050005GetBasePathTest 09:49:30 11:23:02.890 INFO - Test 'SscuMimo050005GetBasePathTest' exceeded execution timeout period. 09:49:30 11:23:02.890 INFO - 09:49:30 11:54:28.022 INFO - timeout Test RohdeSchwarz.Contest.PhysicalDevicesTests/SscuMimoTest/SscuMimo0004GetPathListTestPtp 09:49:30 11:54:28.022 INFO - Test 'SscuMimo0004GetPathListTestPtp' exceeded execution timeout period. 09:49:30 11:54:28.022 INFO - 11:23:03 12:49:28.408 INFO - timeout Test RohdeSchwarz.Contest.PhysicalDevicesTests/SscuMimoTest/SscuMimo0004GetPathListTest 11:23:03 12:49:28.408 INFO - Test 'SscuMimo0004GetPathListTest' exceeded execution timeout period. 11:23:03 12:49:28.408 INFO - 11:54:28 13:27:03.297 INFO - timeout Test RohdeSchwarz.Contest.PhysicalDevicesTests/SscuMimoTest/SscuMimo0005GetBasePathTest 11:54:28 13:27:03.297 INFO - Test 'SscuMimo0005GetBasePathTest' exceeded execution timeout period. 11:54:28 13:27:03.297 INFO - 12:49:27 13:41:13.160 INFO - failed Test RohdeSchwarz.Contest.PhysicalDevicesTests/SmbvTest/Smbv8000OptionCheck6GpsSatellitesTest 12:49:27 13:41:13.160 INFO - Assert.IsTrue failed. The file SmbvGps6SatellitesConfigurationParameters.xml was not deployed. 12:49:27 13:41:13.188 INFO -at RohdeSchwarz.Contest.UnitTests.UnitTestHelper.ActivateConfigurationParameterFile(String deployedFileName, String deviceName) in d:\Snapshots\RunSonarContestBase\contest_sw\CommonFunctions\UnitTestHelper\UnitTestHelper.cs:line 236 13:27:01 13:41:13.188 INFO -at SmbvTest.SmbvTest.Smbv8000OptionCheck6GpsSatellitesTest() in d:\Snapshots\RunSonarContestBase\contest_sw\Devices\PhysicalDevicesTest\SmbvTest\SmbvTest.cs:line 3083 13:27:01 13:41:13.188 INFO - 13:27:01 13:41:13.188 INFO - Environment: Windows 7 64 bit, latest and greatest Jenkins Project: Jenkins Priority: Major Reporter: Dirk Kuypers 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] [ui-samples] (JENKINS-18429) Improve UI Samples
toomasr resolved JENKINS-18429 as Fixed Improve UI Samples Change By: toomasr (17/Jul/13 12:38 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] [robot-plugin] (JENKINS-18675) Failure in suite teardown does not fail test cases
Jussi Malinen commented on JENKINS-18675 Failure in suite teardown does not fail test cases This seems fairly major. Should be fixed on next release. 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] [robot-plugin] (JENKINS-18080) Jenkins slave cannot connect to Master using jnlp
jpiironen commented on JENKINS-18080 Jenkins slave cannot connect to Master using jnlp Hi, Can you elaborate how this relates to the Robot Framework plugin? 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] [robot-plugin] (JENKINS-18230) Parsing output xml: Failed!
Jussi Malinen assigned JENKINS-18230 to Jussi Malinen Parsing output xml: Failed! Change By: Jussi Malinen (17/Jul/13 1:09 PM) Assignee: jpiironen JussiMalinen 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] [robot-plugin] (JENKINS-16158) Delete button disappeared
Jussi Malinen assigned JENKINS-16158 to Jussi Malinen Delete button disappeared Change By: Jussi Malinen (17/Jul/13 1:14 PM) Assignee: jpiironen JussiMalinen 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] [robot-plugin] (JENKINS-15234) Robot plugin should mark build as unstable if there are failed non-critical tests
Jussi Malinen updated JENKINS-15234 Robot plugin should mark build as unstable if there are failed non-critical tests Fair enough, this could be useful. It is not a bug really though, but a new feature. Change By: Jussi Malinen (17/Jul/13 1:23 PM) Issue Type: Bug NewFeature Priority: Major Minor 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-18796) Promoted Parameter String not valorised in publish-over-ssh Script (Exec command)
j morille created JENKINS-18796 Promoted Parameter String not valorised in publish-over-ssh Script (Exec command) Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 17/Jul/13 1:24 PM Description: In a Promotion process, create a "Parameter String" : MY_PROMOTION_PARAMTER_STRING In a Send Build artefact over SSH Add a Exec command script : echo '--- SSH Script' echo $MY_PROMOTION_PARAMTER_STRING And to compare to wanted result In a Shell Script echo '--- Local Script' echo $MY_PROMOTION_PARAMTER_STRING During promotion the value is not evaluated. Environment: Linux Project: Jenkins Priority: Major Reporter: j morille 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] [robot-plugin] (JENKINS-15191) Robot icon is scaled ugly in many places
Jussi Malinen updated JENKINS-15191 Robot icon is scaled ugly in many places Change By: Jussi Malinen (17/Jul/13 1:24 PM) Issue Type: Bug Improvement Priority: Major Minor 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-17751) Link from triggering promotion to triggered build
Greg Smith commented on JENKINS-17751 Link from triggering promotion to triggered build Can one of the owners of this plugin please pull this feature? I would be happy to help test. I think this would be a great addition. 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] [ivy] (JENKINS-18790) Ivy job type should support fingerprinting of consumed dependencies
Timothy Bingaman commented on JENKINS-18790 Ivy job type should support fingerprinting of consumed dependencies This was something I had planned (and very much wanted) to do, but I didn't get time, and haven't had time since then to even support this plugin really. The solution is pretty straightforward, but would take a bit of work. The basic approach is to attach an IvyListener to the build process which can then filter through all of the different IvyEvent objects fired during the build process, recording the resolve events to fingerprint all dependencies and recording the publish events for automatic archiving and fingerprinting of artifacts. The Jenkins Artifactory plugin already has a lot of this code for its integration with the Jenkins Ivy plugin, so their general approach could likely just be copied. I really am not going to have any time at all to work on this though, so I can only hope that some other dev will eventually come along and implement 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] [robot-plugin] (JENKINS-13911) robot plugin when -Parsing output xml
Jussi Malinen resolved JENKINS-13911 as Cannot Reproduce robot plugin when -Parsing output xml Change By: Jussi Malinen (17/Jul/13 1:29 PM) Status: Open Resolved Resolution: CannotReproduce 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] [robot-plugin] (JENKINS-13911) robot plugin when -Parsing output xml
Jussi Malinen updated JENKINS-13911 robot plugin when -Parsing output xml This is impossible to reproduce. We can open this again if we could reproduce this. 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] [robot-plugin] (JENKINS-10617) Non RobotFramework Files being copied from Directory of Robot Output
Jussi Malinen resolved JENKINS-10617 as Fixed Non RobotFramework Files being copied from Directory of Robot Output As Lars Nordin commented, this has already been fixed. Change By: Jussi Malinen (17/Jul/13 1:30 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] [robot-plugin] (JENKINS-9626) Delays the onset jenkins, depending on the workspace volume.
Jussi Malinen commented on JENKINS-9626 Delays the onset jenkins, depending on the workspace volume. Is this still an 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] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick assigned JENKINS-18641 to sogabe People View does Not Populate (makeStaplerProxy) I was thinking it had to be something like that. Not sure how to capture this in the existing functional test, or if we need to; can just leave it for other possible regressions in ProgressiveRendering usage. @sogabe if you can reproduce with the JQuery plugin installed, but not after applying your patch, then go ahead and merge it! Change By: Jesse Glick (17/Jul/13 1:32 PM) Assignee: ssogabe sogabe 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-18589) Deadlock
SCM/JIRA link daemon commented on JENKINS-18589 Deadlock Code changed in jenkins User: Stefan Hirche Path: src/main/java/hudson/ivy/AbstractIvyProject.java http://jenkins-ci.org/commit/ivy-plugin/802921415942bc9c90e81d07ce05910c856bfaae Log: Triggers is not a field anymore, it's a method now, following fix for issue JENKINS-18589 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-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) @sogabe, yes, I have it installed. Good catch. 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] [robot-plugin] (JENKINS-15327) Publish Robot Framework test results not support chinese character
Jussi Malinen assigned JENKINS-15327 to Jussi Malinen Publish Robot Framework test results not support chinese character Change By: Jussi Malinen (17/Jul/13 1:47 PM) Assignee: jpiironen JussiMalinen 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] [robot-plugin] (JENKINS-14366) Robot plugin doesn't handle suite names properly when multiple suites are being ran
Jussi Malinen assigned JENKINS-14366 to Jussi Malinen Robot plugin doesnt handle suite names properly when multiple suites are being ran Change By: Jussi Malinen (17/Jul/13 1:47 PM) Assignee: jpiironen JussiMalinen 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-18641) People View does Not Populate (makeStaplerProxy)
SCM/JIRA link daemon commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Code changed in jenkins User: ssogabe Path: core/src/main/resources/lib/layout/progressiveRendering.jelly http://jenkins-ci.org/commit/jenkins/c2db894ad5ee41a8fd6148bc840e2b82780944f1 Log: JENKINS-18641 st:bind tag adds script tag. This extra tag caused syntax error. 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-18641) People View does Not Populate (makeStaplerProxy)
SCM/JIRA link daemon commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Code changed in jenkins User: Seiji Sogabe Path: core/src/main/resources/lib/layout/progressiveRendering.jelly http://jenkins-ci.org/commit/jenkins/8c8219114dcfd5bb2b63715f6aa33465a584a91b Log: Merge pull request #844 from ssogabe/JENKINS-18641 FIXED JENKINS-18641 st:bind tag adds script tag. This extra tag caused syntax error if JQuery plugin enabled. Compare: https://github.com/jenkinsci/jenkins/compare/1ecf4b14d7be...8c8219114dcf 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-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Tobias Peters commented on JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 I'm running ver. 1.520 jenkins uses the browsers language setting to determin gui language, in Firefox it is under Firefox Preferences Content Languages the node configuration page is, Jenkins Manage Jenkins Manage Nodes node_name Configuration http://jenkins_host:7070/jenkins/computer/node_name/configure I'm not quite sure if I did grasp your server distibution right though. My Configuration is 'master' on windows, which is checking out svn just fine, and multiple slaves started via ssh from the master on linux (gentoo I think) which did have the utf-8 issues when checking out svn repos. the prefix command is only a setting for starting slaves via ssh You running multiple 'master' jenkins servers? from the looks of it the 2 proccesses you have is (pid: 924) jenkins master server, the one with jenkins.war (pid: 26158) jenkins job process and the environment variables you posted seem to be from the job process (pid: 26158), the svn checkout, at least for the slaves but I assume this goes for the master as well, are executed in the environment / process from the node in your case it should be the pid 924, so you would have to check that process and maybe adjust the startupto include language setting 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-18641) People View does Not Populate (makeStaplerProxy)
SCM/JIRA link daemon resolved JENKINS-18641 as Fixed People View does Not Populate (makeStaplerProxy) Change By: SCM/JIRA link daemon (17/Jul/13 1:54 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-18641) People View does Not Populate (makeStaplerProxy)
SCM/JIRA link daemon commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Code changed in jenkins User: ssogabe Path: changelog.html http://jenkins-ci.org/commit/jenkins/0f515fe81064ad414f166beb82a6d47d59f61e21 Log: updated changelog for JENKINS-18641 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] [tap] (JENKINS-17947) Nested TAP not parsed correctly
Bruno P. Kinoshita commented on JENKINS-17947 Nested TAP not parsed correctly Confirmed it's a bug in tap4j 1. Already fixed, cutting a new release. Will bump up the tap4j dependency version and will test again to see if the exception is gone. 1 https://github.com/tupilabs/tap4j/issues/12 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] [debian-package-builder] (JENKINS-18797) Debian post-inst clobbers working jenkins configuration with obsolete hudson configuration if /var/lib/hudson still exists
Marius Gedminas created JENKINS-18797 Debian post-inst clobbers working jenkins configuration with obsolete hudson configuration if /var/lib/hudson still exists Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: debian-package-builder Created: 17/Jul/13 2:31 PM Description: Background: I had Hudson installed from http://hudson-ci.org/debian. I upgraded Ubuntu from 10.04 LTS to 12.04 LTS. I installed Jenkins 1.424 from stock Ubuntu repos (and ended up with both Hudson and Jenkins installed side by side, which was kind of nice for a gradual migration) I moved all the jobs from Hudson to Jenkins manually, cleaning them up as I went, then shut down Hudson and disabled its startup script As time passed I kept making changes to Jenkins (new jobs, etc.) Summary of the situation: a hudson package is still installed from the old hudson-ci repo jenkins and jenkins-common packages are installed from Ubuntu repos /var/lib/hudson exists with old configuration /var/lib/jenkins exists with new configuration /var/lib/jenkins is a mountpoint for an ext4 filesystem (/var was too small) What I did next: added http://pkg.jenkins-ci.org/debian to apt sources tried to apt-get dist-upgrade to get the latest jenkins What I expected: jenkins is upgraded and doesn't destroy my working configuration in /var/lib/jenkins What actually happened: important configuration files like /var/lib/jenkins/config.xml and /var/lib/jenkins/.gitconfig were overwritten with stale copies from /var/lib/hudson It's a good thing I had a backup! There were other speedbumps along the road, and I'll file separate bugs for them: a conflict with a file from Ubuntu's jenkins-common, which I had to resolve by manually apt-get removing jenkins-common, after which I could run apt-get install jenkins again to continue the upgrade jenkins's post-install script failed with a bunch of errors like mv: inter-device move failed: `/var/lib/hudson/jobs' to `/var/lib/jenkins/jobs'; unable to remove target: Is a directory and to continue I had to mv /var/lib/hudson /var/lib/hudson.DO-NOT-TOUCH and run dpkg --configure --pending. Environment: Ubuntu 12.04 LTS Project: Jenkins Priority: Major Reporter: Marius Gedminas 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-18589) Deadlock
Johno Crawford commented on JENKINS-18589 Deadlock @kohsuke any ideas on how to maintain backward compatibility for ivy-plugin? or should we bump required core to 1.5xx? for (Trigger? trigger : getTriggers().values()) might be an option albeit ugly.. 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] [debian-package-builder] (JENKINS-18798) Please support upgrades from Ubuntu's jenkins packages
Marius Gedminas created JENKINS-18798 Please support upgrades from Ubuntus jenkins packages Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: debian-package-builder Created: 17/Jul/13 2:38 PM Description: Please add the appropriate Conflicts/Replaces: jenkins-common Debian package headers so that the 'jenkins' package from http://pkg.jenkins-ci.org/debian can be used to upgrade from 'jenkins' in Ubuntu's primary repository. Testing procedure: get a virtual machine running Ubuntu 12.04 or later (older releases did not have a 'jenkins' package) sudo apt-get install jenkins # this also pulls in jenkins-common etc. wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add - echo deb http://pkg.jenkins-ci.org/debian binary/ | sudo tee /etc/apt/sources.list.d/jenkins.list sudo apt-get update sudo apt-get dist-upgrade Expected result: the 'jenkins' package from pkg.jenkins-ci.org replaces the jenkins/jenkins-common packages from Ubuntu Actual result: dpkg: error processing /var/cache/apt/archives/jenkins_1.523_all.deb (--unpack): trying to overwrite '/usr/share/jenkins/jenkins.war', which is also in package jenkins-common 1.424.6+dfsg-1ubuntu0.1 Environment: Ubuntu 12.04 LTS Project: Jenkins Priority: Minor Reporter: Marius Gedminas 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] [www] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Marius Gedminas created JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: www Created: 17/Jul/13 2:59 PM Description: One of my jobs produces plain-text files that are in UTF-8. When I view them at /job/jobname/ws/filename.txt, I see garbage because Jenkins serves them with Content-Type: text/plain;charset=ISO-8859-1 Jenkins's /systemInfo says file.encoding: UTF-8 sun.jnu.encoding: UTF-8 and environment variables contain LANG en_US.UTF-8 so I've no idea why Jenkins thinks it should use Latin-1 instead. Project: Jenkins Priority: Major Reporter: Marius Gedminas 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] [maven] (JENKINS-18459) IOException: No Such File
Jörg Herbst commented on JENKINS-18459 IOException: No Such File I got the same issue on my maschine (jenkins as WAR on tomcat6 on opensuse). After a lot of research we found JENKINS-18578. Jenkins will create a JAR cache in the home directory of the user running tomcat. The home of tomcat6 on opensuse is /usr/share/tomcat6 in my case, but the owner is root, so tomcat cannot create any files or directories here. I've create a .jenkins directory manually and changed the owner to tomcat, now everything is working again. Maybe this helps. 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] [maven] (JENKINS-18459) IOException: No Such File
Fabrice Bacchella commented on JENKINS-18459 IOException: No Such File Yes, it works for me. The build failure are now my own. So bugs 15120 is irrelevant as far as i know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-16042) NullPointer when collecting successful results
hagzag assigned JENKINS-16042 to Oren Weinberg NullPointer when collecting successful results Change By: hagzag (17/Jul/13 2:53 PM) Assignee: OrenWeinberg 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
SCM/JIRA link daemon resolved JENKINS-18701 as Fixed winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Change By: SCM/JIRA link daemon (17/Jul/13 3:16 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
SCM/JIRA link daemon commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Code changed in jenkins User: Nicolas De Loof Path: src/java/winstone/tools/WinstoneControl.java http://jenkins-ci.org/commit/winstone/b3ebfeb7b3d6db95f90f8ae2374dc065f8f65db4 Log: FIXED JENKINS-18701 map legacy log levels (1:9) to java.util.logging.Level 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-13703) AJP support does not respect the specs. breaks with SSL
SCM/JIRA link daemon commented on JENKINS-13703 AJP support does not respect the specs. breaks with SSL Code changed in jenkins User: Fritz Elfert Path: src/java/winstone/ajp13/Ajp13IncomingPacket.java http://jenkins-ci.org/commit/winstone/f5ee736f2e3acb8516ec30c00ee308d6601fe966 Log: Fix JENKINS-13703 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=scm_issue_linkavatarId=10371;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=scm_issue_link
id=email_scm_issue_link
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=scm_issue_link;
style=color:#355564;SCM/JIRA link daemon/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
[JIRA] [core] (JENKINS-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
SCM/JIRA link daemon commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Code changed in jenkins User: Kohsuke Kawaguchi Path: src/java/winstone/tools/WinstoneControl.java http://jenkins-ci.org/commit/winstone/6bbe9e1ad1e1273af9d4cbd1d66ce449b952e177 Log: Merge pull request #10 from ndeloof/master FIXED JENKINS-18701 map legacy log levels (1:9) to java.util.logging.Level Compare: https://github.com/jenkinsci/winstone/compare/38a84316b449...6bbe9e1ad1e1 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-18800) Jenkins selects channel to wrong node for build job
Martin Schröder created JENKINS-18800 Jenkins selects channel to wrong node for build job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, ssh Created: 17/Jul/13 3:58 PM Description: In the last 12 months, we have encountered a very rare, but also very critical issue in Jenkins core or the SSH-Slaves plug-in. The issue is that Jenkins spontaneously enters a state in which it reproducibly selects the wrong channel for some of its connected build hosts. All build hosts are connected via the SSH-Slaves plug-in. This immediately leads failing builds, as they will not respect the workspace locks anymore, as they lock them on the correct host, but talk with a different host to execute builds. A typical log-output looks like this: --- 14:45:35 Started by command line by user 14:45:35 Building remotely on musxbird039 in workspace /local/jenkins_workspace/workspace/PROJECT ... 14:45:35 Checkout:GIT-REPO / /local/jenkins_workspace/workspace/PROJECT - hudson.remoting.Channel@37ecb28e:musxbird029 --- As you can see, it selects musxbird039 for building, but uses the channel to musxbird029. Since the workspace is usually physically present on those machines, too, the build starts. Unfortunately, since the workspace is only locked on musxbird039, but not on musxbird029, a collision can occur freely. This leads, of course, to a vast variety of build failures. We do not know of a way to reliably reproduce this issue, as it appears randomly after some time. Sometimes it takes months to appear, sometimes only days. The only known way of repairing the bug is to disconnect both machines and let them restart their slaves and all their associated threads on the Jenkins master. Rebooting the server itself obviously also works. We are quite frankly stumped by this bug. Even examining the slave-channel allocation code of Jenkins ourselves did not lead to any clue. If you need more information, we will be happy to give them. Best regards, Martin Schröder Intel Mobile Communications GmbH. Environment: Ubuntu 12.04 64-bit Jenkins LTS 1.509.1 Java(TM) SE Runtime Environment (build 1.6.0_45-b06) 64-bit Project: Jenkins Labels: core node slave slaves jenkins ssh channel linux Priority: Critical Reporter: Martin Schröder 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-18800) Jenkins selects channel to wrong node for build job
Martin Schröder updated JENKINS-18800 Jenkins selects channel to wrong node for build job Change By: Martin Schröder (17/Jul/13 4:03 PM) Environment: Ubuntu12.0464-bitJenkinsLTS1.509.1Java(TM)SERuntimeEnvironment(build1.6.0_45-b06)64-bit JenkinsSSHplugin2.3JenkinsSSHSlavesplugin0.27 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-18800) Jenkins selects channel to wrong node for build job
Martin Schröder updated JENKINS-18800 Jenkins selects channel to wrong node for build job Change By: Martin Schröder (17/Jul/13 4:04 PM) Environment: Ubuntu12.0464-bit JenkinsLTS1.509.1 Java(TM)SERuntimeEnvironment(build1.6.0_45-b06)64-bitJenkins LTS1.509.1Jenkins SSHplugin2.3JenkinsSSHSlavesplugin0.27 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] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Kohsuke Kawaguchi commented on JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail As of 1.520, core has moved on to Java6, so currently this is expected. To quote the changelog, "Core started relying on Java 1.6 as per the agreement in the dev list. If you have a serious objection against it, please let us know before we really start relying on 1.6 features." 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] [ghprb] (JENKINS-18713) push --force loses build statuses
Iulian Dragos edited a comment on JENKINS-18713 push --force loses build statuses I just noticed that this only happens when using GitHub notifications. If I go back to polling, things look good. 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] [ghprb] (JENKINS-18713) push --force loses build statuses
Iulian Dragos commented on JENKINS-18713 push --force loses build statuses I just notice that this only happens when using GitHub notifications. If I go back to polling, things look good. 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-8606) ThinBackup only backs one job out of 10, and continually runs in the background
Thomas Fürer resolved JENKINS-8606 as Fixed ThinBackup only backs one job out of 10, and continually runs in the background Hi bob, this is not related to the original issue, which is fixed. the newer problem is related to https://issues.jenkins-ci.org/browse/JENKINS-17475, which I'm currently working on. So please vote for JENKINS-17475 where I close this issue. Change By: Thomas Fürer (17/Jul/13 4:22 PM) Status: Reopened 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] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Jyrki Puttonen commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently I have three slaves and each of them have multiple executors. There's two different jobs which both allocate a port with name ARQUILLIAN. Both of these jobs have concurrent builds. Now only one build gets executed at a time, leaving other slaves and executors unused. Other builds stay in the queue with text "Blocked by running build". When the running build is completed, next one starts. At some times, multiple builds are assigned to executors, but only one of them is actually running. Others are just waiting with empty consoles. So, answers to your questions: Do the queued builds continue once the build holding the blocked port has completed? Yes, they do Is a build on one slave being blocked because a port is being used on another slave? Yes Do you have a use case where you need all of the slaves to start running but then block during the build? No, I just need one random port assigned to one job. 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] [custom-tools] (JENKINS-18707) CustomTools plugin doesn't work properly on Multi-configuration builds
SCM/JIRA link daemon commented on JENKINS-18707 CustomTools plugin doesnt work properly on Multi-configuration builds Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/customtools/multiconfig/MulticonfigWrapperOptions.java src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper/config.jelly src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper/help-name.html src/main/webapp/CustomToolInstallWrapper/help-multiconfigOptions.html src/main/webapp/CustomToolInstallWrapper/help-skipInstallationOnMaster.html src/test/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallerTest.java http://jenkins-ci.org/commit/customtools-plugin/fb74c915170eb5992b51a8864ae693586000375b Log: Added option: Skip installation on MatrixBuild https://issues.jenkins-ci.org/browse/JENKINS-18707 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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] [custom-tools] (JENKINS-18707) CustomTools plugin doesn't work properly on Multi-configuration builds
SCM/JIRA link daemon commented on JENKINS-18707 CustomTools plugin doesnt work properly on Multi-configuration builds Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/customtools/multiconfig/MulticonfigWrapperOptions.java src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper/config.jelly src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper/help-name.html src/main/webapp/CustomToolInstallWrapper/help-multiconfigOptions.html src/main/webapp/CustomToolInstallWrapper/help-skipInstallationOnMaster.html src/test/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallerTest.java http://jenkins-ci.org/commit/customtools-plugin/33caac66f1b4b9fbaabacf837ddea69a1776968b Log: Merge pull request #4 from synopsys-arc-oss/JENKINS-18707-matrix-build-support New option: Skip tools installation on MatrixBuild's master job Compare: https://github.com/jenkinsci/customtools-plugin/compare/53001e138555...33caac66f1b4 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] [customtools-plugin] (JENKINS-13285) customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher
Oleg Nenashev assigned JENKINS-13285 to Oleg Nenashev customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher Change By: Oleg Nenashev (17/Jul/13 4:41 PM) Assignee: recampbell OlegNenashev 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=scm_issue_linkavatarId=10371;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=scm_issue_link
id=email_scm_issue_link
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=scm_issue_link;
style=color:#355564;SCM/JIRA link daemon/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
[JIRA] [maven] (JENKINS-16920) Running native Maven projects on JDK 5 using Jenkins hosted on Tomcat 7 fails
Jesse Glick resolved JENKINS-16920 as Wont Fix Running native Maven projects on JDK 5 using Jenkins hosted on Tomcat 7 fails As of 1.520, core has moved on to Java6, so currently this is expected. To quote the changelog: Core started relying on Java 1.6 as per the agreement in the dev list. If you have a serious objection against it, please let us know before we really start relying on 1.6 features. Change By: Jesse Glick (17/Jul/13 4:46 PM) Status: Open Resolved Resolution: WontFix 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] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Jesse Glick commented on JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail The pom.xml of the library has no compiler plugin configuration and thus creates code for whatever JDK it runs on (Java 6 class version 50) Not true; the JNR POM specifies maven.compiler.target1.6/maven.compiler.target as of 1.0.0. (The Maven compiler plugin always uses a deterministic source/target level, regardless of the JDK used to run Maven. If unspecified, it currently defaults to JDK 5.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Jesse Glick updated JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail While there is no current plan to fix this in the sense of restoring the ability to run Maven on JDK 5, I will investigate making the plugin behave more gracefully when JDK 5 is selected for the project. Change By: Jesse Glick (17/Jul/13 4:51 PM) Labels: jdk regression Assignee: JesseGlick 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] [perforce] (JENKINS-18801) perforce sync not working in multi depot environment
robsimon created JENKINS-18801 perforce sync not working in multi depot environment Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 17/Jul/13 5:45 PM Description: 1) have multi-depot environment like: //aaa/ //bbb/ //ccc/ 2) have a workspace mapping like: //bbb/backup_Jenkins/xyz/... //Jenkins_Config/xyz/... 3) Check "Always Force Sync" 4) see in the job Console output the following Using master perforce client: Jenkins_Config workspace $ p4 workspace -o Jenkins_Config Saving modified client Jenkins_Config workspace $ p4 -s client -i Last build changeset: 269197 workspace $ p4 changes -s submitted -m 1 //Jenkins_Config/... Sync'ing workspace to changelist 269197 (forcing sync of unchanged files). workspace $ p4 -s sync -f //Jenkins_Config/...@269197 Sync complete, took 118 ms Expected: Files from depot source //bbb/backup_Jenkins/xyz/... are checked-out to workspace. Result: The workspace remains empty. However, if the mapping gets changed to: //bbb/backup_Jenkins/xyz/... //Jenkins_Config/bbb/xyz/... Note, that the depot name appears again then the files are checked-out into the workspace. Nevertheless, I don't want the extra directory (bbb) for various reasons in my workspace and the first mapping should work as well. Environment: perforce plugin v1.3.24, jenkins v1.5.17, Java jre1.7.0_17_64, Windows 7 Enterprise SP1, Perforce Server P4D/LINUX26X86_64/2012.2/585708 Project: Jenkins Priority: Major Reporter: robsimon 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
Łukasz Jąder commented on JENKINS-18312 changelog browsing uses the wrong path to Redmine FYI I've made commit access request https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/LEVW1VvJ5OA to be able to address also this issue. Please consider 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=dogfoodavatarId=10372;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=dogfood
id=email_dogfood
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=dogfood;
style=color:#355564;dogfood/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-5753'JENKINS-5753/a
/div
[JIRA] [perforce] (JENKINS-18801) perforce sync not working in multi depot environment
Rob Petti commented on JENKINS-18801 perforce sync not working in multi depot environment Can you post your whole client mapping, please? I've been using multi-depot specs for years without any issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
SCM/JIRA link daemon commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/f611e2566ec9512661168270c16d0b474c088c1d Log: JENKINS-18701 Noting. 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] [translation] (JENKINS-17333) Some Spanish translations encoding mistakes
SCM/JIRA link daemon resolved JENKINS-17333 as Fixed Some Spanish translations encoding mistakes Change By: SCM/JIRA link daemon (17/Jul/13 6:31 PM) Status: InProgress 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] [translation] (JENKINS-17333) Some Spanish translations encoding mistakes
SCM/JIRA link daemon commented on JENKINS-17333 Some Spanish translations encoding mistakes Code changed in jenkins User: Harald Albers Path: core/src/main/resources/jenkins/management/Messages_es.properties http://jenkins-ci.org/commit/jenkins/d385b9ffc056cb09e7dd7b52c8c7770767e1d0c5 Log: FIXED JENKINS-17333 Some Spanish translations encoding mistakes 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-8914) Jenkins 1.399: java.lang.UnsupportedClassVersionError: Bad version number in .class file using JmDNS 3.4.0
SCM/JIRA link daemon commented on JENKINS-8914 Jenkins 1.399: java.lang.UnsupportedClassVersionError: Bad version number in .class file using JmDNS 3.4.0 Code changed in jenkins User: Baptiste Mathus Path: pom.xml http://jenkins-ci.org/commit/jenkins/b02b14764d0be6c0e41e9dc12e1d97d9300154b2 Log: Using mojo extra-enforcer-rules enforceBytecodeVersion. This rule enforces a bytecode version in dependencies. This would prevent cases like JENKINS-8914 where someone had introduced a dependency compiled with JDK1.6 at a time where Jenkins was still on 1.5. With 1.7 already here and 1.8 coming, this should help no to do that again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
domi commented on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step Actually, i think this could be done with the current implementation of the conditional build step plugin. Do you wanna have a go with 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] [tap] (JENKINS-17504) TAP Plugin generates bad detail links on tapTestReport page
Bruno P. Kinoshita resolved JENKINS-17504 as Fixed TAP Plugin generates bad detail links on tapTestReport page Change By: Bruno P. Kinoshita (17/Jul/13 7:02 PM) Status: InProgress 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] [git] (JENKINS-12655) GIT_BRANCH is incorrect in build steps when branch choosing strategy is set to inverse (but it is correct in build name macro)
Erik L commented on JENKINS-12655 GIT_BRANCH is incorrect in build steps when branch choosing strategy is set to inverse (but it is correct in build name macro) Still broken in 1.4 plugin and 1.0.7 client 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] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
recampbell resolved JENKINS-15976 as Fixed Provided maven settings.xml in maven builder is lost 40f3b095a claims to have fixed this issue, but was not automatically done for some reason. Change By: recampbell (17/Jul/13 7:19 PM) Status: Reopened Resolved Fix Version/s: current 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-18701) winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
dogfood commented on JENKINS-18701 winstone dont use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL Integrated in jenkins_main_trunk #2723 JENKINS-18701 Noting. (Revision f611e2566ec9512661168270c16d0b474c088c1d) Result = UNSTABLE Jesse Glick : f611e2566ec9512661168270c16d0b474c088c1d Files : 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
SCM/JIRA link daemon commented on JENKINS-17475 Backup stops when processing some file like latestfailedbuild Code changed in jenkins User: tofuatjava Path: src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java http://jenkins-ci.org/commit/thin-backup-plugin/01ccb80bd3dc52b771d36d09a2374e3469b7c93c Log: JENKINS-17475: implement backup for last*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] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
Davi Arnaut commented on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step If asking me, no - please go ahead. 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] [customtools-plugin] (JENKINS-13285) customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher
Oleg Nenashev started work on JENKINS-13285 customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher Change By: Oleg Nenashev (17/Jul/13 8:11 PM) Status: Open InProgress 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] [customtools-plugin] (JENKINS-13285) customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher
Oleg Nenashev commented on JENKINS-13285 customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher Pull request: https://github.com/jenkinsci/customtools-plugin/pull/5 I'll merge it into the next release 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.
