[JIRA] [dry] (JENKINS-22356) No parser found for duplicated code
clausfod
updated JENKINS-22356
No parser found for duplicated code
Change By:
clausfod
(26/Mar/14 7:13 AM)
Description:
Running Jenkins 1.556 on Windows 7 and get this error when running CPD:{code}ava.io.IOException: No parser found for duplicated code results file D:\build\hudson\jobs\
xportalen trunk
xtrunk
CI\workspace\testoutput\pmd\cpd.xml01:08:58.336 at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:99)01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:300)01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:258)01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:209)01:08:58.336 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:178)01:08:58.336 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)01:08:58.336 at hudson.FilePath.act(FilePath.java:914)01:08:58.336 at hudson.FilePath.act(FilePath.java:887)01:08:58.336 at hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:175)01:08:58.336 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:144)01:08:58.336 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)01:08:58.336 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:742)01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714)01:08:58.336 at hudson.model.Build$BuildExecution.post2(Build.java:183)01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663)01:08:58.336 at hudson.model.Run.execute(Run.java:1713)01:08:58.336 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)01:08:58.336 at hudson.model.ResourceController.execute(ResourceController.java:88)01:08:58.336 at hudson.model.Executor.run(Executor.java:231){code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dry] (JENKINS-22356) No parser found for duplicated code
clausfod created JENKINS-22356 No parser found for duplicated code Issue Type: Bug Assignee: Ulli Hafner Components: dry Created: 26/Mar/14 7:12 AM Description: Running Jenkins 1.556 on Windows 7 and get this error when running CPD: ava.io.IOException: No parser found for duplicated code results file D:\build\hudson\jobs\xportalen trunk CI\workspace\testoutput\pmd\cpd.xml 01:08:58.336 at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:99) 01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:300) 01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:258) 01:08:58.336 at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:209) 01:08:58.336 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:178) 01:08:58.336 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) 01:08:58.336 at hudson.FilePath.act(FilePath.java:914) 01:08:58.336 at hudson.FilePath.act(FilePath.java:887) 01:08:58.336 at hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:175) 01:08:58.336 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:144) 01:08:58.336 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) 01:08:58.336 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:742) 01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) 01:08:58.336 at hudson.model.Build$BuildExecution.post2(Build.java:183) 01:08:58.336 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) 01:08:58.336 at hudson.model.Run.execute(Run.java:1713) 01:08:58.336 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 01:08:58.336 at hudson.model.ResourceController.execute(ResourceController.java:88) 01:08:58.336 at hudson.model.Executor.run(Executor.java:231) Project: Jenkins Priority: Major Reporter: clausfod This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameterized-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build
Maik Skorna commented on JENKINS-22325 Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build Thanks Brent ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (JENKINS-19038) Cannot execute a command line
Mathias Giacomuzzi commented on JENKINS-19038 Cannot execute a command line I also like to use Reqtify from 3DS on Jenkins. How do handle that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-flow] (JENKINS-22357) Build Flow checkDsl fails with "Request Entity Too Large"
Wolf Geldmacher created JENKINS-22357 Build Flow checkDsl fails with "Request Entity Too Large" Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 26/Mar/14 8:08 AM Description: During configuration of a flow, as the amount of DSL code to execute in a flow grows, the ~8k limit for GET requests as imposed by Apache can be exceeded, resulting in the message Request Entity Too Large The requested resource /jenkins/view/trunk/job/=flow_trunk/descriptorByName/com.cloudbees.plugins.flow.BuildFlow/checkDsl does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit. Apache/2.2.22 (Debian) Server at xx-ci.xx.ch Port right after the "Define build flow using flow DSL" text entry field. The message is sometimes visible as copied above, at other times only an "ERROR" link is displayed which gets expanded to the message when clicked. Could HTTP POST requests be used instead of HTTP GET requests? Environment: Jenkins 1.551 running under tomcat7/apache2 on debian 7.4 "wheezy" Project: Jenkins Labels: plugin configuration build-flow Priority: Minor Reporter: Wolf Geldmacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
Patrick Roth commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem on 1.532.2, master and slave are Linux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-flow] (JENKINS-22357) Build Flow checkDsl fails with "Request Entity Too Large"
Wolf Geldmacher updated JENKINS-22357 Build Flow checkDsl fails with "Request Entity Too Large" Change By: Wolf Geldmacher (26/Mar/14 8:31 AM) Description: During configuration of a flow, as the amount of DSL code to execute in a flow grows, the ~8k a 4k limit for GET requests as imposed by Apache can be exceeded, resulting in the messageRequest Entity Too LargeThe requested resource/jenkins/view/trunk/job/=flow_trunk/descriptorByName/com.cloudbees.plugins.flow.BuildFlow/checkDsldoes not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.Apache/2.2.22 (Debian) Server at xx-ci.xx.ch Port right after the "Define build flow using flow DSL" text entry field.The message is sometimes visible as copied above, at other times only an "ERROR" link is displayed which gets expanded to the message when clicked.Could HTTP POST requests be used instead of HTTP GET requests? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22358) Jenkins 1.556 gives 'Error 404 Not Found'
davida2009 created JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory, core Created: 26/Mar/14 9:21 AM Description: Since upgrading from Jenkins 1.552 to 1.556 I see the following error when I attempt to login to Jenkins: HTTP ERROR 404 Problem accessing /jenkins/;jsessionid=1vdumbbfrnzw1ikx0jl5mqi6q. Reason: Not Found I can successfully login by deleting the Jenkins cookie in my browser (IE9) but the problem reoccurs later. I am using the latest ActiveDirectory plugin. Project: Jenkins Priority: Major Reporter: davida2009 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dry] (JENKINS-22356) No parser found for duplicated code
Ulli Hafner commented on JENKINS-22356 No parser found for duplicated code And? Without more information I can't help... Which plug-in and Jenkins version? Is the file a valid XML file (correct non-windows encoding?)? can you please attach the cpd.xml file? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22233) Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config
Magnus Sandberg assigned JENKINS-22233 to Magnus Sandberg Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config Change By: Magnus Sandberg (26/Mar/14 9:39 AM) Assignee: bklarson Magnus Sandberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22233) Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config
Magnus Sandberg commented on JENKINS-22233 Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config Quote from documentation: "In Advanced Mode it is preferred to use Views and Patterns to assign priorities rather than directly on Jobs using Priority allowing priorities on Jobs are therefore optional" Have you enabled "Allow Priorities Directly on Jobs" on the main configuration page? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling If you are submitting the same Job several times with different priorities you must also allow parallel execution of that Job. If you do not only one build will actually be in the queue, the rest will be in blocked state and can not be sorted by the PrioritySorter. Could this be the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22233) Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config
Dirk Kuypers commented on JENKINS-22233 Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config Yes, I did. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg assigned JENKINS-22294 to Magnus Sandberg Priority is not used in the scheduling Change By: Magnus Sandberg (26/Mar/14 9:43 AM) Assignee: bklarson Magnus Sandberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dry] (JENKINS-22356) No parser found for duplicated code
clausfod commented on JENKINS-22356 No parser found for duplicated code Hi Ulli, We are using Jenkins 1.556 and I guess it is the DRY plugin: [DRY] Collecting duplicate code analysis files... 01:13:51.751 [DRY] Finding all files that match the pattern **/testoutput/pmd/cpd.xml 01:13:51.751 [DRY] Parsing 1 files in D:\build\hudson\jobs\xportalen trunk CI\workspace 01:13:51.751 [DRY] Parsing of file D:\build\hudson\jobs\xportalen trunk CI\workspace\testoutput\pmd\cpd.xml failed due to an exception: I tried without encoding set in the plugin and with ISO-8859-1 specified withou luck I will attache the file in a moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22233) Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config
Dirk Kuypers edited a comment on JENKINS-22233 Since update to Jenkins 1.555 and Prioritysorter 2.6 the option "Job priority" disapeared in job-config Ups, wrong error, sorry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [unity3d-plugin] (JENKINS-21610) Starting Unity with the flag -force-d3d9-ref doesn't work as intended
lacostej commented on JENKINS-21610 Starting Unity with the flag -force-d3d9-ref doesn't work as intended Manuel, It seems I've found a post about someone managing to achieve what you are trying. http://www.slashgames.org/unity3dwithoutgraphics/ If you have the time, try it out and let me know ! Also feel free to add some documentation to the plugin page ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dry] (JENKINS-22356) No parser found for duplicated code
clausfod updated JENKINS-22356 No parser found for duplicated code Change By: clausfod (26/Mar/14 9:52 AM) Attachment: cpd.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] [accelerated-build-now] (JENKINS-22349) Jenkins can't sync files from MKS server on master node
Ivan Yan started work on JENKINS-22349 Jenkins can't sync files from MKS server on master node Change By: Ivan Yan (26/Mar/14 10:07 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-19096) Findbugs Reporting not working with Maven 3.1
Vadim Dedkov commented on JENKINS-19096 Findbugs Reporting not working with Maven 3.1 My parameters: Jenkins version: 1.544 Jenkins Findbugs Plugin version: 4.56 Findbugs Maven Plugin version: 2.5.2 When I put in goals and options "clean org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I didn'n find findbugs icon and findbugs*.xml-files in build directory, but when I put "clean install org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I found findbugs icon and findbugs*.xml-files in build directory of my project. That is, when I put "install" then findbugs 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] [findbugs] (JENKINS-19096) Findbugs Reporting not working with Maven 3.1
Vadim Dedkov edited a comment on JENKINS-19096 Findbugs Reporting not working with Maven 3.1 My parameters: Jenkins version: 1.544 Jenkins Findbugs Plugin version: 4.56 Findbugs Maven Plugin version: 2.5.2 When I put in goals and options in settings of my job "clean org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I didn'n find findbugs icon and findbugs*.xml-files in build directory, but when I put "clean install org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I found findbugs icon and findbugs*.xml-files in build directory of my project. That is, when I put "install" then findbugs 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] [heavy-job] (JENKINS-22359) Heavy-job plugin to be able to use all executors on a node
Steve Carter created JENKINS-22359 Heavy-job plugin to be able to use all executors on a node Issue Type: Improvement Assignee: Unassigned Components: heavy-job Created: 26/Mar/14 10:52 AM Description: I have some jobs that can't/shouldn't be run concurrently with any other, e.g. a test where we want to measure the runtime with a large input; or a job that housekeeps all the sandboxes which can cause file locking issues. Heavy job plugin with weight set equal to the number of executors fixed my problem but if the number of executors would go up then other jobs would get in in parallel. I propose that a special value, like 0 or "max" or "all" can be put in job weight and the heavy job plugin will occupy all executors. Project: Jenkins Priority: Minor Reporter: Steve Carter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20879) SSH Credentials (private key with passphrase) do not work
Simon Fawkes commented on JENKINS-20879 SSH Credentials (private key with passphrase) do not work Is anyone planning on fixing this issue soon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11374) Add deletion option on "list of Shelved Projects"
SCM/JIRA link daemon commented on JENKINS-11374 Add deletion option on "list of Shelved Projects" Code changed in jenkins User: Christian Galsterer Path: src/main/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectExecutable.java src/main/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectTask.java src/main/java/org/jvnet/hudson/plugins/shelveproject/ShelvedProjectsAction.java src/main/resources/org/jvnet/hudson/plugins/shelveproject/ShelvedProjectsAction/index.jelly src/test/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectExecutableTest.java http://jenkins-ci.org/commit/shelve-project-plugin-plugin/aa537fc52f9589f73af35c875a7b4615a95cdc01 Log: fixes JENKINS-11374 - Add deletion option on "list of Shelved Projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11374) Add deletion option on "list of Shelved Projects"
SCM/JIRA link daemon commented on JENKINS-11374 Add deletion option on "list of Shelved Projects" Code changed in jenkins User: Christian Galsterer Path: src/test/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectExecutableTest.java http://jenkins-ci.org/commit/shelve-project-plugin-plugin/27fbda17d389d77ab4698bbbd5c3f98d53eebb17 Log: fixes JENKINS-11374 - Add deletion option on "list of Shelved Projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10544) "shelve project" button missing on some projects
SCM/JIRA link daemon commented on JENKINS-10544 "shelve project" button missing on some projects Code changed in jenkins User: maselvaraj Path: src/main/java/org/jvnet/hudson/plugins/shelveproject/ItemListenerImpl.java src/test/java/org/jvnet/hudson/plugins/shelveproject/ItemListenerImplTest.java http://jenkins-ci.org/commit/shelve-project-plugin-plugin/7258a6071c624ee432795b3a9e62ce3475422ddb Log: Fix to persist Shelve project property whenever the job is updated this fix would resolve JENKINS-10544 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11374) Add deletion option on "list of Shelved Projects"
SCM/JIRA link daemon commented on JENKINS-11374 Add deletion option on "list of Shelved Projects" Code changed in jenkins User: Ben Patterson Path: src/main/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectExecutable.java src/main/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectTask.java src/main/java/org/jvnet/hudson/plugins/shelveproject/ShelvedProjectsAction.java src/main/resources/org/jvnet/hudson/plugins/shelveproject/ShelvedProjectsAction/index.jelly src/test/java/org/jvnet/hudson/plugins/shelveproject/DeleteProjectExecutableTest.java http://jenkins-ci.org/commit/shelve-project-plugin-plugin/4bbf11f40317484c05d6795f4ec369b9928d81e9 Log: Merge pull request #4 from christiangalsterer/master JENKINS-11374 - Add deletion option on 'list of Shelved Projects' Compare: https://github.com/jenkinsci/shelve-project-plugin-plugin/compare/3ff195012315...4bbf11f40317 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich updated JENKINS-22212 No e-mail sent after failed build triggered from another build Even though I've set to passthrough SVN related info (included revisions) to the downstream job but it didn't work. Maybe problem is, with my setup. I have: upstream job that does 2 SVN checkouts and is triggered by SVN post-commit hook downstream job that deploys changes on staging server downstream job doens't have any SVN related options set up Change By: Alexander Obuhovich (26/Mar/14 11:26 AM) Attachment: SvnRevision_Dont_GetPassedThrough.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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich edited a comment on JENKINS-22212 No e-mail sent after failed build triggered from another build Even though I've set to passthrough SVN related info (included revisions) to the downstream job but it didn't work. Maybe problem is, with my setup. I have: upstream job that does 2 SVN checkouts and is triggered by SVN post-commit hook downstream job that deploys changes on staging server downstream job doesn't have any SVN related options set up See attached "SvnRevision_Dont_GetPasse..." image. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20879) SSH Credentials (private key with passphrase) do not work
Mark Waite commented on JENKINS-20879 SSH Credentials (private key with passphrase) do not work I don't think there is any plan to support ssh keys which require a passphrase. You'll need to use an ssh key which does not require a passphrase. I can confirm that ssh keys without a passphrase work very well both to GitHub and to other ssh repositories (like Debian Linux). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22358) Jenkins 1.556 gives 'Error 404 Not Found'
davida2009 commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Also, after I have managed to login, I cannot change view. If I select a different view I am required to login again but my credentials are refused. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesn't contain a path?) Can you explain why the trailing slash does not work in your case? It works for me with gitweb. Is the problem that it is now done for all repository types? If that is the problem, then it seems reasonable that you create a patch with a test that asserts the failing case is fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build > Fingerprint Plugin helps you!: https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint+Plugin It provides "Fingerprint files" in "Build" step. I've tried it, but it seems that fact, that I have several upstream jobs that trigger a same downstream deployment job and that all are using same "revision.txt" makes it hard for Jenkins to manage. Maybe I should create "projecta_revsision.txt", "projectb_revision.txt" in upstream job and pass that filename as a build parameter to downstream job. Then in fingerprint screen I won't see messages like "revision.txt" was introduced by "projecta" and last used by "projectb". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich edited a comment on JENKINS-22212 No e-mail sent after failed build triggered from another build Fingerprint Plugin helps you!: https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint+Plugin It provides "Fingerprint files" in "Build" step. I've tried it, but it seems that fact, that I have several upstream jobs that trigger a same downstream deployment job and that all are using same "revision.txt" makes it hard for Jenkins to manage. Maybe I should create "projecta_revsision.txt", "projectb_revision.txt" in upstream job and pass that filename as a build parameter to downstream job. Then in fingerprint screen I won't see messages like "revision.txt" was introduced by "projecta" and last used by "projectb". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ghprb] (JENKINS-22157) Web Hook Does not Start a build
Frank K commented on JENKINS-22157 Web Hook Does not Start a build We are seeing the exact same thing on our Jenkins environment. The "polling" system is not reliable so we switched to push (which is also more optimal api wise) only to run in to this particular issue which again results in jobs not being built when they should have been. Saving the configuration does "wake" it up again, something is pretty messed up here! The refspec is however set to +refs/pull/*:refs/remotes/origin/pr/* not sure if that matters here since it does match (and more). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling No that is not the problem in this case. I have parallel execution allowed. I have only one executor that is able to execute the job. I also tested with two jobs running on the same executor, one with high and one with low priority. Both are equally executed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [starteam] (JENKINS-14003) Starteam plugin takes a very long time for code check out
ashay batwal assigned JENKINS-14003 to ashay batwal Starteam plugin takes a very long time for code check out Change By: ashay batwal (26/Mar/14 12:29 PM) Assignee: jan_ruzicka ashay batwal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesn't contain a path?) There is no directory (or virtual directory) called gitweb, it is just a cgi script that is only invoked by gitweb with no trailing slash on our config of apache. I'm sure I could fix this on the apache side. From a higher standpoint - the URL is getting changed unnecessarily, and used to work in version 2.0.1, hence thinking the fix is really something that should be done on the jenkins plugin side. I'm working on getting a presentable fix, but it won't be done for a week as I'm away now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
steve steve commented on JENKINS-22162 no GUI update option for snapshot builds of Jenkins Hi Daniel, this is the output: default Thu Mar 20 17:01:08 CET 2014 http://updates.jenkins-ci.org/update-center.json false true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
steve steve edited a comment on JENKINS-22162 no GUI update option for snapshot builds of Jenkins Hi Daniel, this is the output: default Thu Mar 20 17:01:08 CET 2014 http://updates.jenkins-ci.org/update-center.json false true We're on 1.555 and no button for 1.556 to be found. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
steve steve edited a comment on JENKINS-22162 no GUI update option for snapshot builds of Jenkins Hi Daniel, this is the output for the command you posted: default Thu Mar 20 17:01:08 CET 2014 http://updates.jenkins-ci.org/update-center.json false true We're on 1.555 and no button for 1.556 to be found. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22319) Updating Git plugin causes existing builds to immediately fail
Mark Waite commented on JENKINS-22319 Updating Git plugin causes existing builds to immediately fail I think I can duplicate the failure you're seeing, but I think it is expected behavior rather than a bug. However, based on what I'm observing, I can't see how the job ever worked. I suspect that means I don't understand. Hopefully you can help me better understand. The job definition seems to declare that "Branches to build" is refs/heads/jenkins, but when I clone that repository using the refspec in the job definition, there is no refs/heads/jenkins . I cloned the repository with the command git clone --reference /var/lib/git/mwaite/skrooge.git/ git://anongit.kde.org/skrooge.git I also created a Jenkins job which cloned that same repository and confirmed that there was no .git/refs/heads/jenkins in the cloned repository in Jenkins either. Since there is not a branch named jenkins on the remote repository, I thought it was reasonable that the clone did not create a branch named jenkins on the local repository. Since you said that you're using a branch which will only exist locally on the build slave, I assumed you intended to add the additional behaviour "Check out to specific local branch" and that the name of that local branch would be "jenkins". I don't see that local branch in the job definition. If I define my test job "Branches to build" as "master" or "origin/master" or "*/master" and add the "Check out to specific local branch" and have it execute a single shell build step "git branch", it runs successfully and reports that the current branch is "jenkins". If I define my test job "Branches to build" as "refs/heads/jenkins" it fails to checkout a revision because it cannot resolve refs/heads/jenkins as a git version. Can you clarify where I've misunderstood? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slave-status] (JENKINS-21920) Can't take node offline
Gaige Paulsen commented on JENKINS-21920 Can't take node offline I'm seeing the same thing on 1.555 on OS X 10.9.2 as a master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse] (JENKINS-16204) saving config and job runs fail unless at least 2 JDKs are configured
Harald Albers commented on JENKINS-16204 saving config and job runs fail unless at least 2 JDKs are configured Thanks to @lessonz for PR#11, included in Hudson Fitnesse plugin 1.9. This change still doesn't handle the case where no java installation is configured at all (as described in the steps to reproduce section above). Jenkins can handle this situation by falling back to the default java shell command. You can, for example, perform Maven builds under theses conditions. In such a case, the JDK selection is missing from the Execute fitnesse tests build step configuration. Submitting the configuration leads to a blank page with an unspecific exception being logged to the console, see fitnesse-stacktrace.txt. Release 1.9, however is a big improvement as it resolves the issue for the case with one installed JDK. So, this issue should be changed to something like "use system JDK if no JDK is configured" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse] (JENKINS-16204) saving config and job runs fail unless at least 2 JDKs are configured
Harald Albers updated JENKINS-16204 saving config and job runs fail unless at least 2 JDKs are configured Change By: Harald Albers (26/Mar/14 1:04 PM) Attachment: fitnesse-stacktrace.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fitnesse] (JENKINS-16204) use system java to launch fitnesse if no JDK is configured in Jenkins
Harald Albers updated JENKINS-16204 use system java to launch fitnesse if no JDK is configured in Jenkins Change By: Harald Albers (26/Mar/14 1:06 PM) Summary: saving config and job runs fail unless at least 2 JDKs are use system java to launch fitnesse if no JDK is configured in Jenkins Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-22341) Failure to connect to artifactory server break configuration page
recampbell updated JENKINS-22341 Failure to connect to artifactory server break configuration page Change By: recampbell (26/Mar/14 1:07 PM) Labels: performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21989) ReverseProxySetupMonitor broken in Jenkins release 1.552
Christian Hofstaedtler commented on JENKINS-21989 ReverseProxySetupMonitor broken in Jenkins release 1.552 For nginx, the config change apparently is as follows: (plus this needs nginx 1.1.12 or newer) Bad config: proxy_passhttp://127.0.0.1:9000/; Good config: proxy_passhttp://127.0.0.1:9000; (Note the removed trailing slash.) This is documented behaviour in nginx, but not really obvious. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [naginator] (JENKINS-20065) Retain original build causes
SCM/JIRA link daemon commented on JENKINS-20065 Retain original build causes Code changed in jenkins User: Patrik Boström Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/c54ee58b4b03fb31a12bcb3668684985907fc0fe Log: JENKINS-20065 Retain original build causes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [naginator] (JENKINS-20065) Retain original build causes
SCM/JIRA link daemon commented on JENKINS-20065 Retain original build causes Code changed in jenkins User: Nicolas De loof Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/2bd688aa9568c8ed766c2951f273d350535f4b04 Log: Merge pull request #4 from patbos/JENKINS-20065 JENKINS-20065 Retain original build causes Compare: https://github.com/jenkinsci/naginator-plugin/compare/bb3bb9f5d405...2bd688aa9568 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas
created JENKINS-22360
Missing space in IRC notifications
Issue Type:
Bug
Assignee:
kutzi
Components:
ircbot
Created:
26/Mar/14 1:31 PM
Description:
When a build fails, jenkins messages me privately on IRC to say
Build app isSTILL FAILING: https://...
("app" is the project name, "STILL FAILING" is bold red).
Note the missing space between "is" and the build status.
Public notifications to the channel are also missing a space in front of the build status:
Project app build #2129:STILL FAILING in 19 min: https://...
Environment:
Ubuntu, Jenkins 1.509.2, IRC plugin 2.23, instant-messaging plugin 1.28
Project:
Jenkins
Labels:
irc
plugin
Priority:
Trivial
Reporter:
Marius Gedminas
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-18953) Clover java.lang.IndexOutOfBoundsException
Jesse Glick commented on JENKINS-18953 Clover java.lang.IndexOutOfBoundsException CloverDecoratingLauncher makes no attempt to check whether the command it is decorating is even an Ant command at all! For example: […] $ cleartool endview -server … FATAL: Index: 2, Size: 2 java.lang.IndexOutOfBoundsException: Index: 2, Size: 2 at java.util.ArrayList.rangeCheck(ArrayList.java:604) at java.util.ArrayList.get(ArrayList.java:382) at hudson.plugins.clover.CloverBuildWrapper$CloverDecoratingLauncher.decorateArgs(CloverBuildWrapper.java:224) at hudson.plugins.clover.CloverBuildWrapper$CloverDecoratingLauncher.launch(CloverBuildWrapper.java:199) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.plugins.clearcase.HudsonClearToolLauncher.getLaunchedProc(HudsonClearToolLauncher.java:71) at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:143) at hudson.plugins.clearcase.ClearToolExec.version(ClearToolExec.java:865) at hudson.plugins.clearcase.ClearToolExec.doesSetcsSupportOverride(ClearToolExec.java:181) at hudson.plugins.clearcase.ClearToolExec.setcs(ClearToolExec.java:1079) at hudson.plugins.clearcase.ClearToolExec.setcs2(ClearToolExec.java:770) at hudson.plugins.clearcase.action.BaseSnapshotCheckoutAction.checkout(BaseSnapshotCheckoutAction.java:80) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:383) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [shell-script-scm] (JENKINS-22361) Execute Shell spawning infinite processes
Volodymyr Mykhailyk created JENKINS-22361 Execute Shell spawning infinite processes Issue Type: Bug Affects Versions: current Assignee: Richard Sczepczenski Attachments: environment.txt Components: shell-script-scm Created: 26/Mar/14 1:55 PM Description: Any build with single step for Execute Shell crashes the system by spawning infinte processes like "/bin/sh -xe /tmp/hudson283232498517769135.sh" Steps to reproduce: 1. Create Free-style build 2. Add one build step Execute shell with commands: echo 'step1' echo 'step2' 3. Run the build and inspect new processes via top Note if running similar steps via XShell everything works as expected Environment: Ubuntu 12.0.4 java.version 1.6.0_30 Project: Jenkins Priority: Major Reporter: Volodymyr Mykhailyk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-multijob-plugin] (JENKINS-22362) Multi Job project fails when a phase job fails even when the "Mark phase as successful" is set to "Complete (always continue)" for a phase job
Andres Developer created JENKINS-22362 Multi Job project fails when a phase job fails even when the "Mark phase as successful" is set to "Complete (always continue)" for a phase job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 26/Mar/14 2:15 PM Description: Setting "Mark phase as successful when phase jobs statuses are Complete (always continue)" for a multijob project should continue and not fail if a phase job fails. In 1.9 release there was identical issue reported, which was presumably fixed... Project: Jenkins Priority: Major Reporter: Andres Developer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Utopic Men commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
ikedam commented on JENKINS-22212 No e-mail sent after failed build triggered from another build I think fingerprints use not the name of files, but the content of files. You should output SVN_URL_1 additional to SVN_REVISION_1. I'm not sure how "Include/passthrough Upstream SVN Revisons" work. It may requires checkout also in downstream to have variables defined. "Predefined Parameters" always work and may be reliable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copy-project-link] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Artur Szostak created JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Issue Type: Bug Assignee: Unassigned Components: copy-project-link Created: 26/Mar/14 2:48 PM Description: After upgrading the plugin from version v1.1 to v1.2 and restarting the jenkins instance I no longer see the copy link in the interface and find the following error in the logs: WARNING: Failed to load hudson.plugins.copyProjectLink.CopyFolderActionFactory java.lang.InstantiationException: /opt/jenkins/data/plugins/copy-project-link/WEB-INF/lib/classes.jar might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.copyProjectLink.CopyFolderActionFactory at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:504) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230) at com.google.inject.spi.Elements.getElements(Elements.java:103) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.internal.InjectorImpl.createChildInjector(InjectorImpl.java:230) at hudson.ExtensionFinder$GuiceFinder.refresh(ExtensionFinder.java:336) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2154) at hudson.PluginManager.dynamicLoad(PluginManager.java:431) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1313) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1116) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:701) Caused by: java.lang.ClassNotFoundException: hudson.plugins.copyProjectLink.CopyFolderActionFactory at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:985) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) Environment: Jenkins v1.532.2 Project: Jenkins Priority: Major Reporter: Artur Szostak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Julio Gonzalez Gil commented on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. For me it's happening as well with 1.6.0 and Jenkins 1.537 If jenkins is located at http://jenkins.mycorp.com/jenkins, then some URL for images are written as http://jenkins.mycorp.com/jenkins/jenkins/plugin/build-failure-analyzer/images/* I only have problems with http://jenkins.mycorp.com/jenkins/jenkins/plugin/build-failure-analyzer/images/48x48/information.png on both the build info page and the "build history" box. If Jenkins is installed at root folder (http://jenkins.mycorp.com/) then the route is http://jenkins.mycorp.com//plugin/build-failure-analyzer/images/48x48/information.png (incorrect) but the image loads as one slash is ignored. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build I'm not sure how "Include/passthrough Upstream SVN Revisons" work. Aren't the "parameterized-trigger" plugin developer? It may requires checkout also in downstream to have variables defined. That is my guess 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] [envinject] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Renu Chudamani commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations I don't have any groovy scripts associated to my job - but still got this error. I enabled the envinject and then when I try to disable I get this null pointer error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Julio Gonzalez Gil edited a comment on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. For me it's happening as well with 1.6.0 and Jenkins 1.537 If jenkins is located at http://jenkins.mycorp.com/jenkins, then some URL for images are written as http://jenkins.mycorp.com/jenkins/jenkins/plugin/build-failure-analyzer/images/* I'm problems with http://jenkins.mycorp.com/jenkins/jenkins/plugin/build-failure-analyzer/images/48x48/information.png and http://jenkins.mycorp.com/jenkins/jenkins/plugin/build-failure-analyzer/images/16x16/information.png If Jenkins is installed at root folder (http://jenkins.mycorp.com/) then the route is http://jenkins.mycorp.com//plugin/build-failure-analyzer/images/48x48/information.png (incorrect) but the image loads as one slash is ignored. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [artifactory] (JENKINS-22341) Failure to connect to artifactory server break configuration page
Nicolas De Loof commented on JENKINS-22341 Failure to connect to artifactory server break configuration page https://www.jfrog.com/jira/browse/HAP-466 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [artifactory] (JENKINS-22296) Artifactory Release Staging can't push back to git/Stash Repository
Christopher Timm commented on JENKINS-22296 Artifactory Release Staging can't push back to git/Stash Repository We were able to solve the problem by ourselfes. The problem was not directly related to this plugin. It was a problem with this plugin, used in on a Windows machine: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin We followed the directions and especially the part of "Some windows fun". We had to put the id_rsa and id_rsa.pub in the directory: C:\Program Files(x86)\Git\.ssh So apparently the credentials to pull from the git repository are not the ones used by this plugin to push to the repository. Best regards. Christopher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [artifactory] (JENKINS-22296) Artifactory Release Staging can't push back to git/Stash Repository
Christopher Timm resolved JENKINS-22296 as Fixed Artifactory Release Staging can't push back to git/Stash Repository Already commented on the issue with an explanation of what was wrong. Change By: Christopher Timm (26/Mar/14 3:32 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] [violations] (JENKINS-22364) Jenkins Violation Plugin Does Not Populate "XML Filename Pattern"
Sean McCully created JENKINS-22364 Jenkins Violation Plugin Does Not Populate "XML Filename Pattern" Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-03-26 at 10.10.42 AM.png, Screen Shot 2014-03-26 at 10.17.16 AM.png Components: violations Created: 26/Mar/14 3:31 PM Description: After enabling Violations Plugin and choosing pattern for "checkstyle", populating "Filename Pattern", applying changes and then reloading page. The violations plugin does not properly display the previously saved file name pattern. This causes an issue if changes are saved again, resetting the value for the file name pattern. Environment: Jenkins 1.550 Chrome 33.0.1750.152 Firefox 28 Project: Jenkins Priority: Major Reporter: Sean McCully This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. If substitution can be done on the build definition/workspace name, what would be the expectation wrt polling? Or are these builds triggered by other builds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Note to self: Another request for ability to substitute the build defn/workspace name 309370: Jazz RTC plugin for Jenkins does not accept parameters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [shell-script-scm] (JENKINS-22361) Execute Shell spawning infinite processes
Volodymyr Mykhailyk commented on JENKINS-22361 Execute Shell spawning infinite processes Not sure what caused the issue. However after clean install of jenkins everything got back to normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22365) Cannot install latest version of scm-sync-configuration plugin
Paul DeCoursey created JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 26/Mar/14 3:48 PM Description: I attempted to install this plugin and I get this error. java.io.IOException: Failed to download from http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.7.4/scm-sync-configuration.hpi at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:781) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1125) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1285) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1103) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:701) Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://updates.jenkins-ci.org/download/plugins/scm-sync-configuration/0.0.7.4/scm-sync-configuration.hpi at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) Project: Jenkins Priority: Major Reporter: Paul DeCoursey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22365) Cannot install latest version of scm-sync-configuration plugin
Paul DeCoursey commented on JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin Might be related to using the github oauth plugin for authentication. I turned off authentication and it installed fine... unless it was just down and now it's better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15607) SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar
Paul DeCoursey commented on JENKINS-15607 SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar Might be related to using the github oauth plugin for authentication. I turned off authentication and it installed fine... unless it was just down and now it's better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15607) SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar
Paul DeCoursey commented on JENKINS-15607 SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar oops, wrong one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Magnus Sandberg commented on JENKINS-22294 Priority is not used in the scheduling OK, please turn on some logging as described on the wiki, this will tell exactly what priorities are used and when (and why) jobs are moved to the executor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-20709) CLI client hangs
Marco Miller commented on JENKINS-20709 CLI client hangs (Please note that the above pingers-disabling hypothesis was inconclusive as we were trying it out.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesn't contain a path?) Did get enough time to do this today, so have submitted a pull request for review https://github.com/jenkinsci/git-plugin/pull/217 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [buildtriggerbadge] (JENKINS-22366) BuildTriggerBadge should have a dedicated icon for Gerrit Trigger
Baptiste Mathus created JENKINS-22366 BuildTriggerBadge should have a dedicated icon for Gerrit Trigger Issue Type: Improvement Assignee: Baptiste Mathus Components: buildtriggerbadge Created: 26/Mar/14 4:56 PM Description: Currently, Gerrit trigger will display the fallback icon (question mark). Would be great to support a dedicated icon. Project: Jenkins Priority: Trivial Reporter: Baptiste Mathus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22367) Move JDKInstaller to a plugin
Larry Shatzer, Jr. created JENKINS-22367 Move JDKInstaller to a plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Mar/14 5:23 PM Description: When Oracle changes the cookie name they use to check if you have agreed to the license agreement, it currently requires a core change to make this happen. It would be best if the JDKInstaller was its own plugin, so we can just update the plugin, and that will allow older Jenkins installs to upgrade, if necessary. Project: Jenkins Priority: Critical Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
kutzi commented on JENKINS-22360 Missing space in IRC notifications There's clearly a space after is, as you can confirm for yourself: https://github.com/jenkinsci/instant-messaging-plugin/blob/master/src/main/java/hudson/plugins/im/build_notify/BuildToChatNotifier.java#L66 Have you confirmed that this is not some visual artifact or your IRC client - e.g. C&P the message into a Text editor to see if there's really no whitespace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
kutzi edited a comment on JENKINS-22360 Missing space in IRC notifications There's clearly a space after 'is', as you can confirm for yourself: https://github.com/jenkinsci/instant-messaging-plugin/blob/master/src/main/java/hudson/plugins/im/build_notify/BuildToChatNotifier.java#L66 Have you confirmed that this is not some visual artifact or your IRC client - e.g. C&P the message into a Text editor to see if there's really no whitespace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22365) Cannot install latest version of scm-sync-configuration plugin
Frédéric Camblor commented on JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin Don't know where this 0.0.7.4 comes from. I didn't released it, and there doesn't seem to be any commit/tag on github about 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] [openid] (JENKINS-22368) Discovery fails when Jenkins is behind a proxy
Justin Harringa created JENKINS-22368 Discovery fails when Jenkins is behind a proxy Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: openid Created: 26/Mar/14 6:41 PM Description: The OpenId plugin doesn't work properly when attempting to discover the provider. My specific case is with the Google provider. I confirmed that I could access the URL with Jenkins by testing the Google URL in the proxy settings screen (I have also been downloading plugins, etc). Upon inspection of the code, I noticed that the constructor that calls the discovery method in openid4java never initialized HttpClient with the HttpClientFactory. This was only occurring in the getManager() method. Here is an example of the log entry. Mar 24, 2014 3:37:46 PM org.apache.catalina.core.ApplicationContext log SEVERE: Error while serving http://someserver.mydomain.com/jenkins/configureSecurity/configure java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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 org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.Appl
[JIRA] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
Daniel Beck commented on JENKINS-22162 no GUI update option for snapshot builds of Jenkins As you can see from the output, the update center data is almost a week old. Go to Manage Plugins » Advanced. Click Check Now (lower right). Wait on the "Checking Updates..." page until it says "Done". Then re-run the script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22347) Allow Jenkins to download JDK8
dogfood commented on JENKINS-22347 Allow Jenkins to download JDK8 Integrated in jenkins_main_trunk #3257 [FIXED JENKINS-22347] Allow JDK8 to be downloaded. Left in other cookie for backwards compatability. (Revision 8b69e7e305f45f9981cc182b6725c6314a32b5e2) JENKINS-22347 Update changelog. (Revision 2347573cecccd75d4808e0a7657e6cdeb9e5) Result = SUCCESS kohsuke : 8b69e7e305f45f9981cc182b6725c6314a32b5e2 Files : core/src/main/java/hudson/tools/JDKInstaller.java kohsuke : 2347573cecccd75d4808e0a7657e6cdeb9e5 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22365) Cannot install latest version of scm-sync-configuration plugin
Paul DeCoursey commented on JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin very odd. Jenkins claims that is the version I have installed now that I got it installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17391) "Use private Maven repository" at jobs being overriden by global jenkins configuration
evernat commented on JENKINS-17391 "Use private Maven repository" at jobs being overriden by global jenkins configuration Is it reproduced with a recent version of the Maven plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22369) Cannot save a job after a Choice parameter is deleted
Robert Parker created JENKINS-22369 Cannot save a job after a Choice parameter is deleted Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 26/Mar/14 7:32 PM Description: Under Jenkins 1.556, after making changes to the configuration of a job that involve deleting a "choice parameter" in a parameterized build, it is not possible to save the job. Project: Jenkins Priority: Major Reporter: Robert Parker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sauce-ondemand] (JENKINS-22370) NullPointerException when launching sauce connect
Nick Guilford created JENKINS-22370 NullPointerException when launching sauce connect Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 26/Mar/14 7:57 PM Description: I recently upgraded from v1.61 to v1.75 of Sauce OnDemand plugin for Jenkins v1.524. After doing so, all jobs using the plug-in encounter Null Pointer Exception when launching sauce-connect. Job/SlaveDetails: Sauce connect launched on slave Slave had already been created and running jobs with Sauce Connect before the plug-in update Configured to use web driver Uses default sauce connect credentials (i.e. those set up in the master plug-in configuration) Bringing the slave offline, restarting it, and bringing it back online did not solve the problem Plug-in Configuration Details: "Sauce Connect Working Directory" field blank "Disable Sauce Status Column?" unchecked "Use authentication details in ~/.sauce-ondemand?" unchecked Test Connection returns success Log: Starting Sauce OnDemand SSH tunnel on slave node Launching Sauce Connect on ... FATAL: null java.lang.NullPointerException at hudson.plugins.sauce_ondemand.PluginImpl.get(PluginImpl.java:116) at com.saucelabs.hudson.HudsonSauceConnectFourManager.getSauceConnectWorkingDirectory(HudsonSauceConnectFourManager.java:14) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.createProcessBuilder(SauceConnectFourManager.java:89) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:172) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:542) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:517) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Environment: Jenkins version 1.524 Sauce OnDemand version 1.71 Jenkins master: Linux 2.6.32-45-server #104-Ubuntu SMP Tue Feb 19 21:35:01 UTC 2013 x86_64 GNU/Linux Jenkins slave: Linux 2.6.35.14-r36223-p36091-amd64 #4 SMP Tue May 15 00:29:13 PDT 2012 x86_64 GNU/Linux Project: Jenkins Priority: Blocker Reporter: Nick Guilford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sauce-ondemand] (JENKINS-22370) NullPointerException when launching sauce connect
Nick Guilford updated JENKINS-22370 NullPointerException when launching sauce connect Change By: Nick Guilford (26/Mar/14 7:59 PM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [openid] (JENKINS-22368) Discovery fails when Jenkins is behind a proxy
Justin Harringa
updated JENKINS-22368
Discovery fails when Jenkins is behind a proxy
Change By:
Justin Harringa
(26/Mar/14 8:01 PM)
Description:
The OpenId plugin doesn't work properly when attempting to discover the provider. My specific case is with the Google provider. I confirmed that I could access the URL with Jenkins by testing the Google URL in the proxy settings screen (I have also been downloading plugins, etc). Upon inspection of the code, I noticed that the constructor that calls the discovery method in openid4java never initialized
the proxy settings for
HttpClient with the HttpClientFactory. This was only occurring in the getManager() method. Here is an example of the log entry. {noformat}Mar 24, 2014 3:37:46 PM org.apache.catalina.core.ApplicationContext logSEVERE: Error while serving http://someserver.mydomain.com/jenkins/configureSecurity/configurejava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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 org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.in
[JIRA] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Sam Xiao commented on JENKINS-20769 Failed to execute command Pipe.EOF It happens to me as well: Jenkins ver. 1.532.2 Ubuntu 12.04 SEVERE: Failed to execute command Pipe.EOF(165) (channel bob-10.69) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(165) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(386) (channel bob-10.16) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(386) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds] (JENKINS-22371) Promoted step job process stuck in a waiting loop, hang forever, can't abort
Sam Xiao created JENKINS-22371 Promoted step job process stuck in a waiting loop, hang forever, can't abort Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: promoted_steps.png Components: promoted-builds Created: 26/Mar/14 8:17 PM Description: Jenkins 1.532.2 (LTS) Ubuntu 12.04 24GB of RAM We are trying to promote a build in the "promoted step", and it went to have this hanging waiting loop forever. `jenkins.log` gives this, not sure it's related or not: SEVERE: Failed to execute command Pipe.EOF(165) (channel bob-10.69) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(165) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(386) (channel bob-10.16) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(386) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Mar 26, 2014 1:10:55 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(7127) (channel loopback_deployer) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:10:55 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(7127) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Mar 26, 2014 1:11:14 PM hudson.model.Run execute Try to abort it, but have this error: No such file: /var/lib/jenkins/jobs/test_project/promotions/1 - Deploy to Today/builds/2014-03-26_10-06-50/log See attached for the screenshot Project: Jenkins
[JIRA] [core] (JENKINS-22371) Promoted step job process stuck in a waiting loop, hang forever, can't abort
Sam Xiao updated JENKINS-22371 Promoted step job process stuck in a waiting loop, hang forever, can't abort Change By: Sam Xiao (26/Mar/14 8:17 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-22372) envinject script content fails to run on slave unless another plugin in job provides buildWrapper in config
Trevor Baker created JENKINS-22372 envinject script content fails to run on slave unless another plugin in job provides buildWrapper in config Issue Type: Bug Assignee: Gregory Boissinot Attachments: thisFAILS.xml, thisFAILS_log.txt, thisPASSES.xml, thisPASSES_log.txt Components: envinject Created: 26/Mar/14 8:34 PM Description: Trivial EnvInject "script contents" throw java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/slavehome/jenkins") It seems like the script is attempting to run on the master using the slaves jenkinsHome dir. The script contents run correctly if I add a build tool plugin that provides a tool to the environment. I've attached a job config that fails and its log, plus a working job and log where I added a build tool. The build tool installation apparently delays the "script content" execution until after the build tool install, which ensures the CWD is actually on the slave and not master when the "script content" is run. Environment: Jenkins 1.556 envinject 1.89 tomcat 7.x Project: Jenkins Priority: Major Reporter: Trevor Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20500) Build queue is not filtered after progress updated
Jesse Glick assigned JENKINS-20500 to Jesse Glick Build queue is not filtered after progress updated Change By: Jesse Glick (26/Mar/14 8:54 PM) Assignee: Kohsuke Kawaguchi 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] [core] (JENKINS-20500) Build queue is not filtered after progress updated
Jesse Glick started work on JENKINS-20500 Build queue is not filtered after progress updated Change By: Jesse Glick (26/Mar/14 8:54 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [www] (JENKINS-19639) cc.xml includes job only from default view
Daniel Beck commented on JENKINS-19639 cc.xml includes job only from default view I don't think this is a bug, maybe you deliberately want to include only a subset of jobs? If you have an 'All' view, just access /view/All/cc.xml instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder] (JENKINS-20004) Links from Build History in folder broken
Jesse Glick resolved JENKINS-20004 as Duplicate Links from Build History in folder broken Change By: Jesse Glick (26/Mar/14 9:17 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] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder
Jesse Glick commented on JENKINS-19310 Incorrect links in build history when view is defined inside a folder jobBaseURL is just too fragile and probably needs to go away. BuildListTable should instead produce absolute URLs. It could be given a View ancestor so that it could check whether a job is a member of the given view, and if so, link to it via that view. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Jon Proietti commented on JENKINS-20941 Stored git credentials not used when submodule is updated For me, the solution was to update the sub-modules in a batch script prior to the build. I created a new SSH keypair and saved the public key to the bitbucket user (keypair saved to C:\users\USERNAME\.ssh) Then I ssh'd into g...@bitbucket.com to generate a known_hosts file. Since Jenkins runs as a Windows service, I copied my SSH keys (id_rsa, id_rsa.pub, known_hosts) from C:\users\USERNAME\.ssh to C:\Windows\SysWOW64\config\systemprofile\.ssh. After that was all sorted, I added a build step (needs to be the first build step). I created a Windows batch command that contained the following entries: git config submodule.SUBMODULENAME.url g...@bitbucket.org:SUBMODULE/DIRECTORY.git <-- ssh access url git submodule update --init --recursive This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18128) Filtering build queue/executors does not work in nested view
Jesse Glick updated JENKINS-18128 Filtering build queue/executors does not work in nested view After fixing JENKINS-20500 I see no problems with folders. Change By: Jesse Glick (26/Mar/14 9:36 PM) Component/s: cloudbees-folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
