[JIRA] [cygpath] (JENKINS-22650) POSIX paths are not converted to Windows with Cygpath Plugin
Alexey Pakseykin updated JENKINS-22650 POSIX paths are not converted to Windows with Cygpath Plugin Change By: Alexey Pakseykin (17/Apr/14 6:49 AM) Summary: POXIS POSIX pathsarenotconvertedtoWindowswithCygpathPlugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Wilco Greven commented on JENKINS-22196 Validation error when choosing a valid project as manual downstream project Hello Thomas, The description is not very clear, now that I read it again, sorry for that. But the issue should be easy to reproduce using the following steps: 1. Create a new folder. 2. Create a new project in the folder. In the next steps we will add a manual trigger that triggers this project. 3. Create a new Maven project in the folder. 4. In the Maven project created in step 3 add a 'Build other projects (manual step)' post-build action to trigger the project created in step 2. You should see that validation of the project name fails and it suggests that the project is in the parent folder. It is essential that the project created in step 3 is a Maven project. The versions I used are Jenkins 1.532.2 and build-pipeline-plugin 1.4.2. Wilco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann created JENKINS-22651 Could not copy slave.jar into ... on slave Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 17/Apr/14 7:57 AM Description: Since one of the last updates I cannot connect a slave, which is running a different java version. Jenkins is version 1.558 with Oracle Java 1.7.0_51 and the slave is an x86 box using OpenJDK 1.6.0_27. It is impossible to switch to another Java version on the node. If I try to establish the connection, it fails with this output: [04/17/14 09:46:48] [SSH] Opening SSH connection to alpine_2_7_x86:22. [04/17/14 09:46:48] [SSH] Authentication successful. [04/17/14 09:46:48] [SSH] The remote users environment is: HOME='/home/jenkins' IFS=' ' LOGNAME='jenkins' MAIL='/var/mail/jenkins' OPTIND='1' PATH='/usr/bin:/bin:/usr/sbin:/sbin' PPID='429' PS1='\w \$ ' PS2=' ' PS4='+ ' PWD='/home/jenkins' SHELL='/bin/ash' SSH_CLIENT='10.42.23.23 51323 22' SSH_CONNECTION='10.42.23.23 51323 10.42.23.192 22' USER='jenkins' [04/17/14 09:46:48] [SSH] Checking java version of java [04/17/14 09:46:48] [SSH] java -version returned 1.6.0_27. [04/17/14 09:46:48] [SSH] Starting sftp client. [04/17/14 09:46:48] [SSH] SFTP failed. Copying via SCP. [04/17/14 09:46:48] [SSH] Copying latest slave.jar... hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins/ci' on slave at hudson.plugins.sshslaves.SSHLauncher.copySlaveJarUsingSCP(SSHLauncher.java:1056) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1015) at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:126) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:656) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:523) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJarUsingSCP(SSHLauncher.java:1054) ... 8 more Caused by: java.io.IOException: Remote scp terminated unexpectedly. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) at com.trilead.ssh2.SCPClient.put(SCPClient.java:519) ... 9 more [04/17/14 09:46:48] [SSH] Connection closed. [04/17/14 09:46:48] Launch failed - cleaning up connection The connection itself is opened successfully and if I put slave.jar from another node onto this one, it get's deleted during the above steps. But then scp fails!? Any ideas? The connection to another node with the same OpenJDK version but x86_64 architecture works without any problems. Project: Jenkins Priority: Major Reporter: Yves Schumann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis] (JENKINS-22652) ConcurrentModificationException when Matrix project with dynamic axis starts
Or Shachar created JENKINS-22652 ConcurrentModificationException when Matrix project with dynamic axis starts Issue Type: Bug Affects Versions: current Assignee: Or Shachar Components: dynamic-axis Created: 17/Apr/14 8:20 AM Description: I have a Matrix job with dynamic axis that can run concurrently. When triggering that job several times simultaneously with different axis, I often get this error message: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) at java.util.ArrayList$Itr.next(ArrayList.java:791) at java.util.AbstractCollection.addAll(AbstractCollection.java:333) at java.util.LinkedHashSet.init(LinkedHashSet.java:169) at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:284) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:592) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:345) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) at hudson.model.Run.execute(Run.java:1592) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) I believe that the problem is with the rebuild() method that returns a pointer to a changeable list. Environment: Jenkins 1.509.3 running on Redhat 6.3 with tomcat 7 Project: Jenkins Labels: matrix dynamic-axis Priority: Major Reporter: Or Shachar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis] (JENKINS-22652) ConcurrentModificationException when Matrix project with dynamic axis starts
Or Shachar started work on JENKINS-22652 ConcurrentModificationException when Matrix project with dynamic axis starts Change By: Or Shachar (17/Apr/14 8:33 AM) 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/d/optout.
[JIRA] [warnings] (JENKINS-22653) Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard
Thomas Ellinger created JENKINS-22653 Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 17/Apr/14 9:13 AM Description: When parsing multiple workspace files (using "GNU Make + GNU C Compiler" Parser), only the last file's parsing results are linked to dashboard. Though, in console output both files are mentioned to be parsed properly. Console Output -- 8 - WARNINGS Parsing warnings in files 'buildTestUnits.log' with parser GNU Make + GNU C Compiler (gcc) WARNINGS Finding all files that match the pattern buildTestUnits.log WARNINGS Parsing 1 files in /var/lib/jenkins/jobs/foo/workspace WARNINGS Successfully parsed file /var/lib/jenkins/jobs/foo/workspace/buildTestUnits.log of module with 1 warnings. WARNINGS Parsing warnings in files 'buildProduct.log' with parser GNU Make + GNU C Compiler (gcc) WARNINGS Finding all files that match the pattern buildProduct.log WARNINGS Parsing 1 files in /var/lib/jenkins/jobs/foo/workspace WARNINGS Successfully parsed file /var/lib/jenkins/jobs/foo/workspace/buildProduct.log of module with 1 warnings. 8 --- Note: Compiler warnings of files are differently After successful build I have two entries "GNU Make + GNU C Compiler Warnings", at the dashboard menu on the left hand side, according to my job configuration. No matter which one is choosed, only the parsing results of the last files are shown, which is Jenkins-URL: http://jenkins:8080/job/foo/buildNo/warnings22Result/ It appears that there is some issue in the hyperlink assignment for the dashboard. Same behavior appears when using combination "Scan console log" + "Scan workspace file" Environment: Debian wheezy, x86_64, Jenkins 1.559, Warnings Plug-in 4.40 Project: Jenkins Priority: Major Reporter: Thomas Ellinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
Christian Lövsund commented on JENKINS-22647 NPE while loading job config I got the same error, my workaround was to remove modules folder. Did this because of the WARNING in: jenkins.log WARNING: could not find file /var/lib/jenkins/jobs/ds-integration-tests/modules/ifs.dev$ReportAnnotationsAsPMD/config.xml Apr 17, 2014 11:18:30 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job ds-integration-tests java.lang.NullPointerException at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:784) at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:782) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:115) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:782) at hudson.model.Items.load(Items.java:278) at jenkins.model.Jenkins$18.run(Jenkins.java:2592) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
Christian Lövsund edited a comment on JENKINS-22647 NPE while loading job config I got the same error, my workaround was to remove modules folder. Did this because of the WARNING in: jenkins.log WARNING: could not find file /var/lib/jenkins/jobs/ds-integration-tests/modules/ifs.dev$ReportAnnotationsAsPMD/config.xml Apr 17, 2014 11:18:30 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job ds-integration-tests java.lang.NullPointerException at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:784) at hudson.maven.MavenModuleSet$3.call(MavenModuleSet.java:782) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:115) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:782) at hudson.model.Items.load(Items.java:278) at jenkins.model.Jenkins$18.run(Jenkins.java:2592) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-22653) Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard
Thomas Ellinger updated JENKINS-22653 Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard Change By: Thomas Ellinger (17/Apr/14 9:32 AM) Description: Whenparsingmultipleworkspacefiles(usingGNUMake+GNUCCompilerParser),onlythelastfilesparsingresultsarelinkedtodashboard.Though,inconsoleoutputbothfilesarementionedtobeparsedproperly.ConsoleOutput--8-[WARNINGS]ParsingwarningsinfilesbuildTestUnits.logwithparserGNUMake+GNUCCompiler(gcc)[WARNINGS]FindingallfilesthatmatchthepatternbuildTestUnits.log[WARNINGS]Parsing1filesin/var/lib/jenkins/jobs/foo/workspace[WARNINGS]Successfullyparsedfile/var/lib/jenkins/jobs/foo/workspace/buildTestUnits.logofmodulewith1warnings.[WARNINGS]ParsingwarningsinfilesbuildProduct.logwithparserGNUMake+GNUCCompiler(gcc)[WARNINGS]FindingallfilesthatmatchthepatternbuildProduct.log[WARNINGS]Parsing1filesin/var/lib/jenkins/jobs/foo/workspace[WARNINGS]Successfullyparsedfile/var/lib/jenkins/jobs/foo/workspace/buildProduct.logofmodulewith1warnings.8---Note: Compilerwarnings Content offilesare ensuredtobe differentlyAftersuccessfulbuildIhavetwoentriesGNUMake+GNUCCompilerWarnings,atthedashboardmenuonthelefthandside,accordingtomyjobconfiguration.Nomatterwhichoneischoosed,onlytheparsingresultsofthelastfilesareshown,whichisJenkins-URL:http://jenkins:8080/job/foo/buildNo/warnings22Result/Itappearsthatthereissomeissueinthehyperlinkassignmentforthedashboard.SamebehaviorappearswhenusingcombinationScanconsolelog+Scanworkspacefile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-22653) Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard
Thomas Ellinger updated JENKINS-22653 Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard Change By: Thomas Ellinger (17/Apr/14 9:34 AM) Description: Whenparsingmultipleworkspacefiles(usingGNUMake+GNUCCompilerParser),onlythelastfilesparsingresultsarelinkedtodashboard.Though,inconsoleoutputbothfilesarementionedtobeparsedproperly.ConsoleOutput--8-[WARNINGS]ParsingwarningsinfilesbuildTestUnits.logwithparserGNUMake+GNUCCompiler(gcc)[WARNINGS]FindingallfilesthatmatchthepatternbuildTestUnits.log[WARNINGS]Parsing1filesin/var/lib/jenkins/jobs/foo/workspace[WARNINGS]Successfullyparsedfile/var/lib/jenkins/jobs/foo/workspace/buildTestUnits.logofmodulewith1warnings.[WARNINGS]ParsingwarningsinfilesbuildProduct.logwithparserGNUMake+GNUCCompiler(gcc)[WARNINGS]FindingallfilesthatmatchthepatternbuildProduct.log[WARNINGS]Parsing1filesin/var/lib/jenkins/jobs/foo/workspace[WARNINGS]Successfullyparsedfile/var/lib/jenkins/jobs/foo/workspace/buildProduct.logofmodulewith1warnings.8---Note:ContentoffilesareensuredtobedifferentlyAftersuccessfulbuildIhavetwoentriesGNUMake+GNUCCompilerWarnings,atthedashboardmenuonthelefthandside,accordingtomyjobconfiguration.Nomatterwhichoneischoosed,onlytheparsingresultsofthelast filesareshown,which file is shown.Botharelinkedtothesame Jenkins-URL:http://jenkins:8080/job/foo/buildNo/warnings22Result/Itappearsthatthereissomeissueinthehyperlinkassignmentforthedashboard.SamebehaviorappearswhenusingcombinationScanconsolelog+Scanworkspacefile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22654) Multi-configuration projects display with wrong Delivery Pipeline Stage Name
Justin Mason created JENKINS-22654 Multi-configuration projects display with wrong Delivery Pipeline Stage Name Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 17/Apr/14 9:37 AM Description: Hi there thanks for the Delivery Pipeline plugin! I've tried to set up a multi-config project with Delivery Pipeline 0.7.4; it mostly works correctly, but in the resulting pipeline visualization, the Stage Name I've specified is ignored, and instead the multi-configuration's "User Defined Axis" is used. Project: Jenkins Priority: Minor Reporter: Justin Mason This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
Lars Martin commented on JENKINS-22647 NPE while loading job config Hi Christian, thanks for the hint. Obviously I ignored the prior warning. Removing the 'modules' folder worked for me too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22655) Release Plugin 2.4.1 don't seems to work with current Jenkins version 1.555
Holger Stolzenberg created JENKINS-22655 Release Plugin 2.4.1 dont seems to work with current Jenkins version 1.555 Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: plugin, release Created: 17/Apr/14 10:33 AM Description: While manually triggering a release build, configured pre- and post release build steps of the Release Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin) seems not to be honoured. We want to change the versions via maven-versions-plugin before and after a release build, but the respective call of the maven goals cannot be found in console log (and poms aren't changed). Calling the maven goals from the command line works as expected. Is this plugin version compatible with Jenkins 1.555? Environment: Debian, Jenkins 1.555, Release Plugin 2.4.1, M2 Release Plugin 0.13.0 Project: Jenkins Labels: plugin release compatibility Priority: Major Reporter: Holger Stolzenberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22656) Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.
Gabor Borbely created JENKINS-22656 Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10. Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 17/Apr/14 11:25 AM Description: ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:538) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:304) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1620) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) The sending is working 8 times / 10. But not all the time, and i dont know why. Environment: Windows Server 2008 R2 x64 - 2CPU - 70GB HDD - Jenkins 1.508 - Email-ext plugin 2.28 Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Gabor Borbely This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-6172) Requirement that alternative maven settings be a relative path is a problem
evernat resolved JENKINS-6172 as Incomplete Requirement that alternative maven settings be a relative path is a problem No response from the reporter, so resolving as incomplete. Change By: evernat (17/Apr/14 11:36 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-13261) Style quick action dropdown menu
evernat resolved JENKINS-13261 as Incomplete Style quick action dropdown menu No response from the reporter, so resolving as incomplete. Change By: evernat (17/Apr/14 11:39 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-427) Cannot check out alias modules from CVS
manmohan negi assigned JENKINS-427 to manmohan negi Cannot check out alias modules from CVS Change By: manmohan negi (17/Apr/14 11:42 AM) Assignee: MichaelClarke manmohannegi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-15864) multi-configuration project ignores slave setting
Peter Eisentraut commented on JENKINS-15864 multi-configuration project ignores slave setting I can confirm this with Jenkins 1.558. I converted a job from a plain job to a multi-configuration job (making a new job and copying all the settings meticulously). The multi-configuration job appears to ignore the setting "Restrict where this project can be run" and always runs on the master node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22657) Unable To Upload To HockeyApp Through Proxy
Steve K created JENKINS-22657 Unable To Upload To HockeyApp Through Proxy Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hockeyapp Created: 17/Apr/14 12:42 PM Description: When I try to upload to HockeyApp I receive the following: Uploading to HockeyApp... /Users/Shared/Jenkins/Home/workspace/iOS Task - Upload Nightly SyncProxyTester To HockeyApp/test.ipa java.net.UnknownHostException: rink.hockeyapp.net at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:333) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:169) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) at hudson.model.Run.execute(Run.java:1725) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Build step 'Upload to HockeyApp' marked build as failure Finished: FAILURE I just switched over from TestFlight (and using the TestFlight plugin) and everything was working with those components. Have I missed something? Environment: OS X (10.8.5), Latest build of Jenkins Project: Jenkins Priority: Major Reporter: Steve K This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22657) Unable To Upload To HockeyApp Through Proxy
Steve updated JENKINS-22657 Unable To Upload To HockeyApp Through Proxy Change By: Steve (17/Apr/14 12:44 PM) Description: WhenItrytouploadtoHockeyAppIreceivethefollowing:UploadingtoHockeyApp.../Users/Shared/Jenkins/Home/workspace/ iOSTask-UploadNightlySyncProxyTesterToHockeyApp test /test.ipajava.net.UnknownHostException:rink.hockeyapp.net atjava.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) atjava.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) atjava.net.Socket.connect(Socket.java:579) atsun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) atorg.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:333) atorg.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123) atorg.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147) atorg.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108) atorg.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415) atorg.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) atorg.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) atorg.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) athockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:169) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) athudson.model.Build$BuildExecution.post2(Build.java:182) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) athudson.model.Run.execute(Run.java:1725) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)BuildstepUploadtoHockeyAppmarkedbuildasfailureFinished:FAILUREIjustswitchedoverfromTestFlight(andusingtheTestFlightplugin)andeverythingwasworkingwiththosecomponents.HaveImissedsomething? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
olamy resolved JENKINS-22647 as Fixed NPE while loading job config Change By: olamy (17/Apr/14 1:01 PM) Status: Open Resolved Assignee: olamy 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/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
olamy commented on JENKINS-22647 NPE while loading job config should be fixed https://github.com/jenkinsci/maven-plugin/commit/d0c41f8432a9dfba3a27a2cfca215b4eaec48613 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-22647) NPE while loading job config
olamy closed JENKINS-22647 as Fixed NPE while loading job config Change By: olamy (17/Apr/14 1:02 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22658) Internal server error
Rickard von Essen
created JENKINS-22658
Internal server error
Issue Type:
Bug
Assignee:
Unassigned
Components:
delivery-pipeline
Created:
17/Apr/14 1:16 PM
Description:
Jenkins v 1.525
Delivery Pipeline plugin v 0.7.4
_javascript_ console:
{{
GET https://jenkins.example.com/view/A_View/view/Test/api/json?_=1397739984320 500 (Internal Server Error)
send jquery.full.js:8240
jQuery.extend.ajax jquery.full.js:7719
updatePipelines pipe.js:2
(anonymous function) pipe.js:19
}}
Stack trace see https://gist.github.com/rickard-von-essen/10981424
Project:
Jenkins
Priority:
Blocker
Reporter:
Rickard von Essen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22649) Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config
Mark Waite commented on JENKINS-22649 Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config Is your git-client-plugin version also running the most recent version (currently 1.8.0)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Mark Waite commented on JENKINS-22640 Notify commit cant find job by URI Are you sure you actually have a job which is using the URL "git+ssh://g...@git.host.ru/user/project.git"? I believe the requirement is that the URL must match exactly in the job definition. Does the problem occur for any other form of URL used in your jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22649) Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config
Mark Waite commented on JENKINS-22649 Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config I was unable to duplicate the problem as you reported it. Can you provide more details, and can you confirm it behaves that way on later attempts? Steps I tried: 1. Create a new freestyle Jenkins project 2. Use CVS as the SCM system, with 1. CVSROOT = :pserver:anonym...@cvs.savannah.gnu.org:/sources/ghostscript 2. Modules remote name = ghostscript/expat 3. Modules local name = expat 3. Build that freestyle Jenkins project, confirm it succeeds 4. Change from CVS to Git by clicking the Git radio button, then entering 1. Repository URL = ""> 5. Save the job 6. Run the job to confirm git clone works This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22649) Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config
Mark Waite edited a comment on JENKINS-22649 Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config I was unable to duplicate the problem as you reported it. Can you provide more details, and can you confirm it behaves that way on later attempts? Steps I tried: 1. Create a new freestyle Jenkins project 2. Use CVS as the SCM system, with 2.1. CVSROOT = :pserver:anonym...@cvs.savannah.gnu.org:/sources/ghostscript 2.2. Modules remote name = ghostscript/expat 2.3. Modules local name = expat 3. Build that freestyle Jenkins project, confirm it succeeds 4. Change from CVS to Git by clicking the Git radio button, then entering 4.1. Repository URL = ""> 5. Save the job 6. Run the job to confirm git clone works This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22649) Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config
Mark Waite edited a comment on JENKINS-22649 Git plugin configuration page: No such property: lib for class: hudson.plugins.git.UserRemoteConfig.config I was unable to duplicate the problem as you reported it. Can you provide more details, and can you confirm it behaves that way on later attempts? Steps I tried: Create a new freestyle Jenkins project Use CVS as the SCM system, with CVSROOT = :pserver:anonym...@cvs.savannah.gnu.org:/sources/ghostscript Modules remote name = ghostscript/expat Modules local name = expat Build that freestyle Jenkins project, confirm it succeeds Change from CVS to Git by clicking the Git radio button, then entering Repository URL = ""> Save the job Run the job to confirm git clone works This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22620) 'Could not checkout null' when trying to checkout sha passed from upstream job
Mark Waite commented on JENKINS-22620 Could not checkout null when trying to checkout sha passed from upstream job Are you certain that commit 79c8eb3d846d09ecedf3b331942d8904cdedf515 is available in the repository where you are trying to perform the checkout? The "Could not checkout null" might be better phrased as "Could not checkout a detached head". It is a known, and expected behavior that the git plugin uses a detached head unless it needs a branch for other purposes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22659) Maven project plugin does not propagte a ERROR: Failed to parse POMs condition as a failure
Martin Lichtin created JENKINS-22659 Maven project plugin does not propagte a ERROR: Failed to parse POMs condition as a failure Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 17/Apr/14 1:45 PM Description: When the Maven build fails with above mentioned error, then the Post Steps run even though "Run only if build succeeds" is checked. Project: Jenkins Priority: Major Reporter: Martin Lichtin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22656) Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.
Alex Earl commented on JENKINS-22656 Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10. The version you are using is pretty old. Please upgrade to the latest and see if you still have an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22656) Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.
Gabor Borbely commented on JENKINS-22656 Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10. I could ask that is it possible in our environment (to upgrade), and i will give you feedback! I need a few days for 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/d/optout.
[JIRA] [git] (JENKINS-22620) 'Could not checkout null' when trying to checkout sha passed from upstream job
Mark Waite edited a comment on JENKINS-22620 Could not checkout null when trying to checkout sha passed from upstream job Are you certain that commit 79c8eb3d846d09ecedf3b331942d8904cdedf515 is available in the repository where you are trying to perform the checkout? The "Could not checkout null" might be better phrased as "Could not checkout a detached head". It is a known, and expected behavior that the git plugin uses a detached head unless it needs a branch for other purposes. Since the output also says that the connection timed out after 10 minutes, you may want to check if the correct credentials have been assigned to the downstream job. Another possibility is to check that you don't have a very large git repository or are using a slow connection so that the clone actually takes more than 10 minutes. If either of those is the case, then you can increase the timeout through the "Additional Behaviours" button where you add "Advanced clone behaviours". There is a field which can adjust the timeout there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-22660) More flexible UI for approved signatures
Jesse Glick created JENKINS-22660 More flexible UI for approved signatures Issue Type: Improvement Assignee: Jesse Glick Components: script-security Created: 17/Apr/14 2:10 PM Description: For more comfortable management of sandboxed scripts, administrators should be able to: Remove individual signatures from the list of those already approved. Add signatures without waiting for them to be attempted. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22578) Nothing happens when POST to jenkins github-webhook url
Kyle Moon commented on JENKINS-22578 Nothing happens when POST to jenkins github-webhook url I've resolved my issue and github webhooks are now properly triggering Jenkins jobs. What finally fixed the issue was regenerating the ssh keys on the Master and slaves. I'm guessing that when we migrated our Master we also migrated the ssh key which was created on the old server. At any rate, once I created new ssh keys and copied them into my Git and Jenkins install directories everything started working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22578) Nothing happens when POST to jenkins github-webhook url
Kyle Moon resolved JENKINS-22578 as Not A Defect Nothing happens when POST to jenkins github-webhook url Generate new ssh keys. Change By: Kyle Moon (17/Apr/14 2:12 PM) Status: Open Resolved Fix Version/s: current Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
SCM/JIRA link daemon commented on JENKINS-13279 Interface with Crowd embedded that runs in Jira Code changed in jenkins User: Patrik Boström Path: src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java http://jenkins-ci.org/commit/crowd2-plugin/6c98944e577bbca02c4dfee1764cc1d5a355d187 Log: JENKINS-13279 Support for Jira embedded Crowd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-22661) Pending script approvals should be deleted if an administrator saves that script
Jesse Glick created JENKINS-22661 Pending script approvals should be deleted if an administrator saves that script Issue Type: Improvement Assignee: Jesse Glick Components: script-security Created: 17/Apr/14 2:12 PM Description: If we are configuring a given script as someone with RUN_SCRIPTS then any prior pending approval (say from Items.load) ought to be deleted, since clearly the script is OK. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
SCM/JIRA link daemon commented on JENKINS-16703 Too many periodic requests to Crowd server Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/de/theit/jenkins/crowd/CrowdConfigurationService.java src/main/java/de/theit/jenkins/crowd/CrowdRememberMeServices.java src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java src/main/java/de/theit/jenkins/crowd/CrowdServletFilter.java src/main/java/de/theit/jenkins/crowd/ErrorMessages.java src/main/resources/crowd.properties src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config.jelly src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-applicationName.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-cookieDomain.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-cookieTokenkey.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpMaxConnections.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyHost.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyPassword.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyPort.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyUsername.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpTimeout.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-password.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-sessionValidationInterval.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-url.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-useProxy.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-useSSO.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help.html src/main/resources/de/theit/jenkins/crowd/help-socketTimeout.html http://jenkins-ci.org/commit/crowd2-plugin/7039baf8288687ee20590011dbd03b85020d2009 Log: FIXED JENKINS-21852 Added http proxy configuration. FIXED JENKINS-18791 Session validation interval saved from ui. FIXED JENKINS-13279 Don't use ssoTokenHelper, work with Embedded Crowd in Jira. JENKINS-16703 More options for connection configuration. Compare: https://github.com/jenkinsci/crowd2-plugin/compare/43588915417a...7039baf82886 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
SCM/JIRA link daemon commented on JENKINS-13279 Interface with Crowd embedded that runs in Jira Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java http://jenkins-ci.org/commit/crowd2-plugin/744eaa81bf3968a251654dc9916807ee5fec8055 Log: Merge branch 'JENKINS-13279' of https://github.com/patbos/crowd2-plugin into patbos-JENKINS-13279 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-18791) session.validationinterval is not saved
SCM/JIRA link daemon commented on JENKINS-18791 session.validationinterval is not saved Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/de/theit/jenkins/crowd/CrowdConfigurationService.java src/main/java/de/theit/jenkins/crowd/CrowdRememberMeServices.java src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java src/main/java/de/theit/jenkins/crowd/CrowdServletFilter.java src/main/java/de/theit/jenkins/crowd/ErrorMessages.java src/main/resources/crowd.properties src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config.jelly src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-applicationName.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-cookieDomain.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-cookieTokenkey.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpMaxConnections.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyHost.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyPassword.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyPort.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpProxyUsername.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-httpTimeout.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-password.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-sessionValidationInterval.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-url.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-useProxy.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help-useSSO.html src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/help.html src/main/resources/de/theit/jenkins/crowd/help-socketTimeout.html http://jenkins-ci.org/commit/crowd2-plugin/7039baf8288687ee20590011dbd03b85020d2009 Log: FIXED JENKINS-21852 Added http proxy configuration. FIXED JENKINS-18791 Session validation interval saved from ui. FIXED JENKINS-13279 Don't use ssoTokenHelper, work with Embedded Crowd in Jira. JENKINS-16703 More options for connection configuration. Compare: https://github.com/jenkinsci/crowd2-plugin/compare/43588915417a...7039baf82886 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Matrix jobs don't honor git timeout setting
Mark Waite closed JENKINS-22547 as Cannot Reproduce Matrix jobs dont honor git timeout setting Change By: Mark Waite (17/Apr/14 2:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Matrix jobs don't honor git timeout setting
Mark Waite resolved JENKINS-22547 as Cannot Reproduce Matrix jobs dont honor git timeout setting Change By: Mark Waite (17/Apr/14 2:19 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/d/optout.
[JIRA] [git] (JENKINS-22457) Git push will trigger a build even though no path matches included regions
Mark Waite closed JENKINS-22457 as Cannot Reproduce Git push will trigger a build even though no path matches included regions Change By: Mark Waite (17/Apr/14 2:21 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-19726) JGIT Error in combination with self signed certificate and https repo
Torsten Schlabach commented on JENKINS-19726 JGIT Error in combination with self signed certificate and https repo Actually, as far as I can tell, this does not only affect the JGit implementation but also the native git implementation. I had a job configured using the native git on a Linux box and was a bit suprised to still see a certification path error message originating from the Java VM like this: Building in workspace /var/lib/jenkins/workspace/Native git tests Cloning the remote Git repository Cloning repository https://github.com/jenkinsci/active-directory-plugin.git Fetching upstream changes from https://github.com/jenkinsci/active-directory-plugin.git ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1933) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1123) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:254) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:410) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null Finished: FAILURE (Just in case you wonder why there would be any issue with the verfification of the certificate of https://github.com/..., I am living behind a corporate proxy which thinks it's a good idea to proxy TLS for me as well and re-package the connection into a new https:// connection with a certificate which belongs to the proxy. You'd run into the very same issue when accessing your own git repo with https:// with any kind of self-signed, expired or non-matching domain certificate.) So quickly checking what org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials actually, does, it says /** Check credentials are valid to access the remote repository (avoids git to interactively request username/password.) */ In other words: It makes a preliminary attempt to access some URL inside your repo just in order to see if any credentials are required and if so, if you are in posession of any valid set of credentials. Only if that test passes, it will call the actual git client (whichever one) to do the real work. In case that test fails with an exception (as opposed to a controlled "no, you're not authorized"), game is over here even before it would fire up any git client at all. And as this checkCredentials test is done inside Java, it won't buy you anything if you have set your native git client to ignore TLS cert issues; you just won't get that far. In order to possibly fix this, I understand one could either omit the whole credentials test as a config option (which would fix the issue for the native client) or introduce an option to tell Java not to try and verify certificates, which I understand depends on the version of the HttpComponents API used. In case the plugin is on the latest version (4.3), here is what would have to be used: http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/ssl/TrustSelfSignedStrategy.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
[JIRA] [msbuild] (JENKINS-22461) New MSBuild release has a space in the installation path; causes msbuild plugin to fail
Dick Ginga commented on JENKINS-22461 New MSBuild release has a space in the installation path; causes msbuild plugin to fail I have hit this also with a path to the solution file containing a space This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22662) A job triggered multiple times displayed incorrectly
Onno van der Straaten created JENKINS-22662 A job triggered multiple times displayed incorrectly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 17/Apr/14 2:41 PM Description: When triggering the same job multiple times, the view displays this incorrectly. Only the last run is displayed, and it is displayed multiple times. Project: Jenkins Priority: Minor Reporter: Onno van der Straaten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Dmitry Moskowski
commented on JENKINS-22640
Notify commit cant find job by URI
Sure, I have copy-pasted git url from job configuration.
I have tried some other url schemas("git://", "https://") but nothing works
Is there any way to debug this on my side?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22656) Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.
Alex Earl commented on JENKINS-22656 Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10. Just as an FYI, the version of Jenkins you are using is pretty old too. If you are looking for a stable release, I would recommend the LTS. I build the email-ext against the latest LTS rather than the latest release (which can be way more ahead). Also, from looking at the stack trace, and the code, I believe this issue was already 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/d/optout.
[JIRA] [ec2] (JENKINS-22663) EC2Cloud#provision excessWorkload doesn't take AMI configurations in account
taksan created JENKINS-22663 EC2Cloud#provision excessWorkload doesnt take AMI configurations in account Issue Type: Bug Assignee: Francis Upton Components: ec2, plugin Created: 17/Apr/14 2:47 PM Description: hudson.plugins.ec2.EC2Cloud.provision has calculates the excessWorkload in a way that doesn't take the ami configurations in account. Because of that, if I configure two diffent AMI's: AMI#1 to handle jobs on label "cloud-1" AMI#2 to handle jobs on label "cloud-2" If AMI#2 has idle online slaves and I start a new job tied to label cloud-1, the provisioner won't provision instances to handle the jobs on cloud-1 because excessWorkload will be negative due to idle slaves on cloud-2. Project: Jenkins Priority: Major Reporter: taksan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22664) BuildDiskUsageAction.build must be transient
Jesse Glick created JENKINS-22664 BuildDiskUsageAction.build must be transient Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 17/Apr/14 2:56 PM Description: ... WARNING hudson.model.RunMap retrieve could not load .../jobs/.../builds/2013-11-19_... hudson.util.IOException2: Unable to read .../jobs/.../builds/2013-11-19_.../build.xml at hudson.XmlFile.unmarshal(XmlFile.java:166) at hudson.model.Run.reload(Run.java:320) at hudson.model.Run.init(Run.java:309) at hudson.model.AbstractBuild.init(AbstractBuild.java:187) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:41) at ... Caused by: com.thoughtworks.xstream.converters.ConversionException: Invalid reference Debugging information reference : ../hudson.plugins.disk__usage.BuildDiskUsageAction/build/actions/org.jvnet.hudson.plugins.DownstreamBuildViewAction class : java.util.concurrent.CopyOnWriteArrayList required-type : java.util.concurrent.CopyOnWriteArrayList converter-type : hudson.util.RobustCollectionConverter path: /build/actions/org.jvnet.hudson.plugins.DownstreamBuildViewAction line number : 143 class[1]: hudson.model.FreeStyleBuild converter-type[1] : hudson.util.RobustReflectionConverter version : not available --- at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:57) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:357) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:290) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:229) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at hudson.XmlFile.unmarshal(XmlFile.java:164) ... 132 more while trying to load ?xml version='1.0' encoding='UTF-8'? build actions ... hudson.plugins.disk__usage.BuildDiskUsageAction plugin="disk-usage@0.23" buildDiskUsage.../buildDiskUsage build class="build" actions ... hudson.plugins.disk__usage.BuildDiskUsageAction reference="../../.."/ org.jvnet.hudson.plugins.DownstreamBuildViewAction plugin="downstream-buildview@1.8" build class="build" reference="../../.."/ downstreamBuilds class="concurrent-hash-map"...
[JIRA] [disk-usage] (JENKINS-22664) BuildDiskUsageAction.build must be transient
Jesse Glick commented on JENKINS-22664 BuildDiskUsageAction.build must be transient Note that Downstream Build View 1.9 addresses this issue too, by using RunAction2 itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22665) BuildPipelineView.MyUserIdCause stores entire hudson.model.User
Jesse Glick created JENKINS-22665 BuildPipelineView.MyUserIdCause stores entire hudson.model.User Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 17/Apr/14 3:11 PM Description: Since MyUserIdCause.user is not transient, the entire User object is serialized to a build record as per $JENKINS_HOME/users/*/config.xml, including dangerous things like a customized API token and credentials. And the class is not static, so it serializes a reference to the BuildPipelineView mentioning it. Example: ?xml version='1.0' encoding='UTF-8'? build actions ... hudson.model.CauseAction causes au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView_-MyUserIdCause plugin="build-pipeline-plugin@1.3.3" userIdper...@somewhere.com/userId user fullNameSome Person/fullName properties jenkins.security.ApiTokenProperty apiTokenOOPS!/apiToken /jenkins.security.ApiTokenProperty com.cloudbees.plugins.credentials.UserCredentialsProvider_-UserCredentialsProperty plugin="credentials@1.9.3" domainCredentialsMap class="hudson.util.CopyOnWriteMap$Hash" entry ... /entry /domainCredentialsMap /com.cloudbees.plugins.credentials.UserCredentialsProvider_-UserCredentialsProperty hudson.model.MyViewsProperty views ... /views /hudson.model.MyViewsProperty hudson.plugins.openid.OpenIdUserProperty plugin="openid@2.3" identifiers stringOOPS!/string /identifiers /hudson.plugins.openid.OpenIdUserProperty ... /properties /user outer-class reference="../user/properties/hudson.model.MyViewsProperty/views/au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView[10]"/ /au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView_-MyUserIdCause /causes /hudson.model.CauseAction ... /actions ... /build A Cause must be a static class with a small serial form. In this case you need only a String userId field; use User.get to retrieve the live object on demand. (Or just use the standard UserIdCause. It is not clear why you felt the need to subclass that.) Project: Jenkins Labels: security Priority: Critical Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shelve-project-plugin] (JENKINS-8063) Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384
Pavel Kudrys commented on JENKINS-8063 Seemingly harmless stacktrace when shelving/unshelving projects in Hudson 1.383 and 1.384 Problem still reproducible with the actual release version of Shelve plugin (ver. 1.4.4) and Jenkins ver. 1.559. Any chance to see it fixed anytime soon? Thank you in advance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Mark Waite commented on JENKINS-22640 Notify commit cant find job by URI You might try extracting the exact URL from each of the config.xml files for the Jenkins jobs on your Jenkins servers, then run the curl command to see if you can find any of the URL's which are reported as having a git consumer for that URL. I have the following lines in my "post-receive" file at home: curl --silent http://127.0.0.1:8080/git/notifyCommit?url="" curl --silent http://127.0.0.1:8080/git/notifyCommit?url="" curl --silent http://127.0.0.1:8080/git/notifyCommit?url="" curl --silent http://127.0.0.1:8080/git/notifyCommit?url="" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-21577) S3 Plugin: Publish Mulitple Artifacts
Joshua K commented on JENKINS-21577 S3 Plugin: Publish Mulitple Artifacts FYI, if you need to add more than one file all going to the same bucket, just add all the patterns in the first artifact description separated by commas as a workaround. If you have to use multiple buckets you have to go in and hack the config.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Gaurav Phadke created JENKINS-22666 No popup window when committing changes to job config for putting in commit message Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 17/Apr/14 3:52 PM Description: I have recently upgraded to Jenkins version 1.559, and with this upgrade I have also upgraded the scm-sync-configuration plugin to version 0.0.7.4. After doing the upgrade when I have made a change to a job configuration and hit save button, I dont get a pop-up window to enter the commit message. However I have noticed that the changes do get commited without a message. This problem does not occur when saving the global jenkins config. When looking through defects list I found https://issues.jenkins-ci.org/browse/JENKINS-14582 which sounded similar to the behaviour I am observing but it is claimed that the defect was fixed in version 0.0.7. It is very important from tracking point of view that there are commit messages along with each commit. I couldn't find any logs that have any information about the error Environment: scm-sync-config 0.0.7.4 Project: Jenkins Priority: Major Reporter: Gaurav Phadke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-22653) Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard
Ulli Hafner resolved JENKINS-22653 as Duplicate Multiple Files parsed, but only warnings of last parsed file shown/linked on dashboard Change By: Ulli Hafner (17/Apr/14 4:07 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports] (JENKINS-22667) Report fails when run from slave
Jon Waite created JENKINS-22667 Report fails when run from slave Issue Type: Bug Assignee: Unassigned Components: cucumber-reports Created: 17/Apr/14 4:24 PM Description: When the cucumber reports are executed on a slave. We see two Test Results links under the project however they both only show the native reports. I believe this issue is due to the cucumber.json not being copied from the salve back to the master. masterthought cucumber reports is performing this step. Environment: Cucumber test are executed on a slave Project: Jenkins Priority: Major Reporter: Jon Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-18015) Breakage on Android SDK r22
Travis Christian commented on JENKINS-18015 Breakage on Android SDK r22 I am also still having this problem in 2.10: 12:12:26 $ C:\Android\android-sdk/platform-tools/adb.exe kill-server 12:12:26 The system cannot find the file specified 12:12:26 FATAL: Cannot run program "C:\Android\android-sdk/platform-tools/aapt.exe" (in directory "E:\project workspace\Target"): CreateProcess error=2, The system cannot find the file specified 12:12:26 java.io.IOException: Cannot run program "C:\Android\android-sdk/platform-tools/aapt.exe" (in directory "E:\project workspace\Target"): CreateProcess error=2, The system cannot find the file specified This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I looked at JENKINS-21980 and even when it looks similar, the effects are different. GitHub report no changes, but they mention no problems with the checkout itself. So I wonder if is the same root cause for this or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder BTW, guidance on how to fix this would be appreciated. I'm willing to spend some time on this, but I have no idea about Jenkins internals or how the plugins hooks to the different jenkins stages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-22668) Source Code Management section defaults to method that is not in use
Neal Storey commented on JENKINS-22668 Source Code Management section defaults to method that is not in use Restarting the service seems to have rectified the issue. But not sure how it got in that state to begin with. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-22668) Source Code Management section defaults to method that is not in use
Neal Storey created JENKINS-22668 Source Code Management section defaults to method that is not in use Issue Type: Bug Assignee: Rob Petti Attachments: plugins.txt, stack trace.txt Components: cvs, perforce Created: 17/Apr/14 4:58 PM Description: I'm using Perforce as my SCM.When I click on Configure for a job, I am presented with only one option, CVS. Most buttons like Advanced do nothing. Jenkins is still up and running jobs, but I'm unable to configure them. Environment: Jenkins ver. 1.559 Ubuntu 12.10 Project: Jenkins Labels: jenkins perforce cvs Priority: Major Reporter: Neal Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-11111) Add SVN author and commit message env vars
Raza Ahmed commented on JENKINS-1 Add SVN author and commit message env vars Is this suppose to work with 1.553 release but I tried but seems not working. I would like to use this to send out build notifications only to the SVN committer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Thomas Carsuzan commented on JENKINS-22196 Validation error when choosing a valid project as manual downstream project Hi Wilco, Which folder are you talkin about ? CloudBees Folders Plugin ? Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22578) Nothing happens when POST to jenkins github-webhook url
Chris Petersen reopened JENKINS-22578 Nothing happens when POST to jenkins github-webhook url I don't have remote Jenkins installations, so this is not an issue with SSH keys for me. I can also make things work by using my old installation files, and things only break when I upgrade. Change By: Chris Petersen (17/Apr/14 5:59 PM) Resolution: NotADefect 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/d/optout.
[JIRA] [cvs] (JENKINS-22668) Source Code Management section defaults to method that is not in use
Rob Petti assigned JENKINS-22668 to Unassigned Source Code Management section defaults to method that is not in use Change By: Rob Petti (17/Apr/14 6:04 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Rick Liu created JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: active-directory-1.36-ok.log, active-directory-1.37-err.log Components: active-directory Created: 17/Apr/14 6:37 PM Description: With the same settings, under 1.36 login is successful. After upgrade to 1.37, the login timed out and unable to login. Attach the log files (level: all) for both 1.36 and 1.37 version. Environment: Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-38-generic x86_64) Jenkins ver. 1.532.3 Project: Jenkins Priority: Major Reporter: Rick Liu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-22300) Need ability to associate public ip address for slave nodes
Matt Ferrante commented on JENKINS-22300 Need ability to associate public ip address for slave nodes I'm running into this as well. I will be attempting a fix for 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/d/optout.
[JIRA] [core] (JENKINS-22670) Linebreak project names less aggressively
Daniel Beck created JENKINS-22670 Linebreak project names less aggressively Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 17/Apr/14 7:47 PM Description: Currently, project names in the executors and paths on the system information page are being broken too aggressively. JENKINS-17030 aimed to prevent layout breaking, but does not allow more than 13 chars in an unbroken row. This frequently leads to very weird line break locations. This should be changed to break longer strings only. Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Dmitry Moskowski commented on JENKINS-22640 Notify commit cant find job by URI Sadly, but no luck. Here is the part of my config and request I tried http://i.imgur.com/4WJpn4K.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22670) Linebreak project names less aggressively
Daniel Beck commented on JENKINS-22670 Linebreak project names less aggressively https://github.com/jenkinsci/jenkins/pull/1195 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim what version of the Maven plugin are you using? I am using 2.0.1 now with Jenkins 1.532.2 and the problem still exists. Now in the 1.532.2 (latest stable) version the maven plugin is separate from the Jenkins system so you need to update the maven plugin after you update Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Were still seeing the problem so I edited my comments above to remove the references about not seeing the problem any longer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim, Looks like you have the latest plugin. After grading from 1.509 I needed to add to a maven property. Global MAVEN_OPTS I made mine have the value -XX:MaxPermSize=256m and that resolved by problem. Worth giving a try at least. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-21786) Performance Per Test Case Mode display type use Max. value instead of Average one !
sumen das commented on JENKINS-21786 Performance Per Test Case Mode display type use Max. value instead of Average one ! Because it take the max response-time, the graph is entirely inconclusive for performance metrics. The average (or median, as in the previous comment) would fix it for now. Eventually, we may also want to have this configurable based on whether to take median, or average or 95-percentile.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-22671) xunit does not find .xsl file located in Jenkins_Home\userContent\xunit\Ranorex
Michael Fowler created JENKINS-22671 xunit does not find .xsl file located in Jenkins_Home\userContent\xunit\Ranorex Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 17/Apr/14 9:01 PM Description: I have placed the ranorex-to-xunit.xsl file in Jenkins_Home\userContent\xunit\Ranorex but Ranorex is not added to the drop-down list in Jenkins even after restarting the service. Environment: Windows 7 / Windows Server 2008 R2 Project: Jenkins Labels: plugin Priority: Major Reporter: Michael Fowler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22640) Notify commit can't find job by URI
Mark Waite commented on JENKINS-22640 Notify commit cant find job by URI You might try relying on curl to escape the "+" embedded in the URL, rather that performing the escape yourself. Something like: curl --silent http://127.0.0.1:8080/git/notifyCommit?url="" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-22300) Need ability to associate public ip address for slave nodes
Matt Ferrante commented on JENKINS-22300 Need ability to associate public ip address for slave nodes https://github.com/jenkinsci/ec2-plugin/pull/84 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22409) API Token no longer working for API calls
Peter Downs commented on JENKINS-22409 API Token no longer working for API calls Experiencing the same issue on Jenkins version 1.558 and Github OAuth version 0.14 – it would be great to not have to downgrade. Any way I can help submit a fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Christian Höltje updated JENKINS-21933 PermGen leaks Here's the # of classes ratcheting up over time. I don't have any jobs that just run early in the morning, so I'm not sure why it ratchets up at that point. Change By: Christian Höltje (17/Apr/14 9:46 PM) Attachment: ClassCount.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-16516) Maked Passwords are shown as input parameters in Build pipeline plugin
Thomas Carsuzan edited a comment on JENKINS-16516 Maked Passwords are shown as input parameters in Build pipeline plugin Now waiting for my MaskedPasswordPlugin pull request to be merged. https://github.com/jenkinsci/mask-passwords-plugin/pull/1 Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-16516) Maked Passwords are shown as input parameters in Build pipeline plugin
Thomas Carsuzan commented on JENKINS-16516 Maked Passwords are shown as input parameters in Build pipeline plugin Now waiting for my MaskedPasswordPlugin pull request to be merged. https://github.com/jenkinsci/envinject-plugin/pull/27 Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-15400) pipeline plugin shows global passwords from 'EnvInject' plugin on build card as common env
Thomas Carsuzan commented on JENKINS-15400 pipeline plugin shows global passwords from EnvInject plugin on build card as common env Now waiting for my EnvInjectPlugin pull request to be merged. https://github.com/jenkinsci/envinject-plugin/pull/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/d/optout.
[JIRA] [build-pipeline] (JENKINS-15400) pipeline plugin shows global passwords from 'EnvInject' plugin on build card as common env
Thomas Carsuzan commented on JENKINS-15400 pipeline plugin shows global passwords from EnvInject plugin on build card as common env Progress made to hide sensitive data in 1.4.3-SNAPSHOT Commit : https://github.com/jenkinsci/build-pipeline-plugin/commit/bf1bedebaf8bc625367669f0e80fe36865355f4c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22669) login failed after upgrade to 1.37 from 1.36
Alex Lombardi commented on JENKINS-22669 login failed after upgrade to 1.37 from 1.36 Seeing the same issue on both a W2K3 and a W2K8 device. Noticed that a backup instance of the active-directory.jpi named active-directory.bak now exists with the old dat. When i renamed the new jpi smething else and made the backup active all worked well, but the system detected an update was again available which caused the same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22672) Make /threadDump easier to navigate
Daniel Beck created JENKINS-22672 Make /threadDump easier to navigate Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 17/Apr/14 10:39 PM Description: The /threadDump page is currently not easy no navigate, especially with a large number of nodes. This should be improved Add "table of contents" listing the nodes Make the node headers stand out more Additionally, the nodes are not sorted, so it's difficult to find a specific one. Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22672) Make /threadDump easier to navigate
Daniel Beck commented on JENKINS-22672 Make /threadDump easier to navigate https://github.com/jenkinsci/jenkins/pull/1196 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22612) Parametrizeds jobs do not save after to exclude a parameter
ikedam updated JENKINS-22612 Parametrizeds jobs do not save after to exclude a parameter Looks same to JENKINS-22275 . Do you use Chrome? Change By: ikedam (17/Apr/14 11:32 PM) Component/s: core Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter
ikedam resolved JENKINS-21851 as Fixed No combinations are built in a scheduled build with Matrix Combinations Parameter Fixed in 1.0.6. Change By: ikedam (17/Apr/14 11:37 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/d/optout.
[JIRA] [rundeck] (JENKINS-21802) Rundeck plugin crashes jenkins on startup
Rob Kelly
reopened JENKINS-21802
Rundeck plugin crashes jenkins on startup
Same issue for me on Scientific Linux 6.5.
The older plugin (3.0 I think) was running fine.
Once I upgraded to the newest version, 3.3, Jenkins fails to startup and aborts.
Disabling the Rundeck plugin allows Jenkins to start.
Jenkins Crash
Running from: /usr/lib/jenkins/jenkins.war
Apr 17, 2014 6:59:14 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
Apr 17, 2014 6:59:16 PM winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
Apr 17, 2014 6:59:16 PM winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
Apr 17, 2014 6:59:16 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Apr 17, 2014 6:59:16 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Apr 17, 2014 6:59:16 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Apr 17, 2014 6:59:17 PM hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to connect
Apr 17, 2014 6:59:17 PM hudson.plugins.im.HudsonIsBusyListener init
INFO: Executor busy listener created
Apr 17, 2014 6:59:17 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Apr 17, 2014 6:59:17 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Apr 17, 2014 6:59:21 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Apr 17, 2014 6:59:22 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
WARNING: Failed to instantiate optional component org.jfrog.hudson.ivy.ArtifactoryIvyConfigurator$DescriptorImpl; skipping
Apr 17, 2014 6:59:24 PM winstone.Logger logInternal
WARNING: Untrapped Error in Servlet
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:76:72: st:include finished
at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25)
at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:76:72: st:include finished
at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
[JIRA] [core] (JENKINS-22612) Parametrizeds jobs do not save after to exclude a parameter
Cleber Pereira commented on JENKINS-22612 Parametrizeds jobs do not save after to exclude a parameter Really works with another browser. Unable to delete in Firefox. Thank you, ikedam. You helped me a lot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Ugis Lazdins commented on JENKINS-20941 Stored git credentials not used when submodule is updated Reproduced also with Jenkins running on OS X machine. But seriously, only 11 people have encountered this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck] (JENKINS-21802) Rundeck plugin crashes jenkins on startup
Rob Kelly commented on JENKINS-21802 Rundeck plugin crashes jenkins on startup Seems to only fail using openjdk. java-1.7.0-openjdk-1.7.0.55-2.4.7.1.el6_5.x86_64 java-1.7.0-openjdk-devel-1.7.0.55-2.4.7.1.el6_5.x86_64 Tried installing older versions of the plugin with the same result. Used https://updates.jenkins-ci.org/download/plugins/rundeck/ to install the old hpi. Ran Jenkins using Oracle Java (jdk1.7.0_55) and the crash does NOT occur. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
