[JIRA] [findbugs] (JENKINS-9676) Cannot publish FindBugs reports from remote node
Sam Talebbeik edited a comment on JENKINS-9676 Cannot publish FindBugs reports from remote node Just to add more data to the bug. I am seeing this with an Jenkins server on Linux and the build slave is also running Linux. The Junit and Cobertura publishers are also installed and they have no problem publishing the results. Jenkins ver. 1.519 Jenkins is running with the Jenkins standard Winstone container findbugs plugin for Jenkins 4.48 findbugs-2.0.2 Ant 1.9.1 Stack trace: [FINDBUGS] Collecting findbugs analysis files... ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /home/jenkinsroot/workspace/findbugs-java at hudson.remoting.Channel@3a421096:linuxbuildslave at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: java.io.IOException: Remote call on linuxserver failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:894) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class edu.umd.cs.findbugs.SortedBugCollection at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:266) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:208) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:145) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:105) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Recording test results Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-12567) Skipped tests should not mark build as UNSTABLE
Nalin Makar resolved JENKINS-12567 as Fixed Skipped tests should not mark build as UNSTABLE Closing as fixed again. Original issue reported in this bug has been fixed. Change By: Nalin Makar (30/Jun/13 6:01 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18206) Total duration of a test class should include the times for the configuration methods
Nalin Makar resolved JENKINS-18206 as Fixed Total duration of a test class should include the times for the configuration methods in v1.2 Change By: Nalin Makar (30/Jun/13 5:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18206) Total duration of a test class should include the times for the configuration methods
SCM/JIRA link daemon commented on JENKINS-18206 Total duration of a test class should include the times for the configuration methods Code changed in jenkins User: Nalin Makar Path: README src/main/java/hudson/plugins/testng/results/ClassResult.java http://jenkins-ci.org/commit/testng-plugin-plugin/36353999cbb71e5859a223f023a2e8d46b822cf7 Log: Fixed: JENKINS-18206 - Total duration of a test class should include the times for the configuration methods Compare: https://github.com/jenkinsci/testng-plugin-plugin/compare/e79c42e007fd...36353999cbb7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-9676) Cannot publish FindBugs reports from remote node
Sam Talebbeik edited a comment on JENKINS-9676 Cannot publish FindBugs reports from remote node Just to add more data to the bug. I am seeing this with an Jenkins server on Linux and the build slave is also running Linux. The Junit and Cobertura publishers are also installed and they have no problem publishing the results. Jenkins ver. 1.519 findbugs plugin for Jenkins 4.48 findbugs-2.0.2 Ant 1.9.1 Stack trace: [FINDBUGS] Collecting findbugs analysis files... ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /home/jenkinsroot/workspace/findbugs-java at hudson.remoting.Channel@3a421096:linuxbuildslave at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: java.io.IOException: Remote call on linuxserver failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:894) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class edu.umd.cs.findbugs.SortedBugCollection at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:266) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:208) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:145) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:105) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Recording test results Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-9676) Cannot publish FindBugs reports from remote node
Sam Talebbeik commented on JENKINS-9676 Cannot publish FindBugs reports from remote node Just to add more data to the bug. I am seeing this with an Jenkins server on Linux and the build slave is also running Linux. The Junit and Cobertura publishers are also installed and they have no problem publishing the results. Jenkins ver. 1.519 findbugs-2.0.2 Stack trace: [FINDBUGS] Collecting findbugs analysis files... ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /home/jenkinsroot/workspace/findbugs-java at hudson.remoting.Channel@3a421096:linuxbuildslave at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: java.io.IOException: Remote call on linuxserver failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:894) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class edu.umd.cs.findbugs.SortedBugCollection at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:266) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:208) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:145) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:105) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Recording test results Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16374) BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE
Nalin Makar commented on JENKINS-16374 BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE kutzi, Responded to your comment on Github. Can you elaborate the issue you foresee? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var="FOO"} for 2.29 doesn't work anymore.
Alex Earl
updated JENKINS-18014
[Email-ext plugin] ${ENV, var="FOO"} for 2.29 doesn't work anymore.
Change By:
Alex Earl
(30/Jun/13 1:57 AM)
Component/s:
token-macro
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var="FOO"} for 2.29 doesn't work anymore.
Alex Earl
resolved JENKINS-18014 as Fixed
[Email-ext plugin] ${ENV, var="FOO"} for 2.29 doesn't work anymore.
This will be fixed in the token macro plugin in 1.8
Change By:
Alex Earl
(30/Jun/13 1:57 AM)
Status:
Reopened
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18206) Total duration of a test class should include the times for the configuration methods
Nalin Makar assigned JENKINS-18206 to Nalin Makar Total duration of a test class should include the times for the configuration methods Change By: Nalin Makar (30/Jun/13 1:56 AM) Assignee: nalin_makar Nalin Makar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16832) Do not show failed builds in trend graph
SCM/JIRA link daemon commented on JENKINS-16832 Do not show failed builds in trend graph Code changed in jenkins User: Nalin Makar Path: README src/main/java/hudson/plugins/testng/TestNGProjectAction.java http://jenkins-ci.org/commit/testng-plugin-plugin/f5c5f07c73d56a6b924bf4066e59d24501f2e2ab Log: Fixed: JENKINS-16832 - Do not show failed builds in trend graph This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16832) Do not show failed builds in trend graph
Nalin Makar resolved JENKINS-16832 as Fixed Do not show failed builds in trend graph in v1.2 Change By: Nalin Makar (30/Jun/13 1:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16832) Do not show failed builds in trend graph
Nalin Makar updated JENKINS-16832 Do not show failed builds in trend graph Change By: Nalin Makar (30/Jun/13 1:34 AM) Issue Type: Improvement Bug Assignee: nalin_makar Nalin Makar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16665) should not show +0 when nothing has changed
Nalin Makar assigned JENKINS-16665 to Nalin Makar should not show +0 when nothing has changed Change By: Nalin Makar (30/Jun/13 1:26 AM) Assignee: nalin_makar Nalin Makar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16665) should not show +0 when nothing has changed
Nalin Makar resolved JENKINS-16665 as Fixed should not show +0 when nothing has changed in v1.2 Change By: Nalin Makar (30/Jun/13 1:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16665) should not show +0 when nothing has changed
SCM/JIRA link daemon commented on JENKINS-16665 should not show +0 when nothing has changed Code changed in jenkins User: Nalin Makar Path: src/main/java/hudson/plugins/testng/util/TestResultHistoryUtil.java http://jenkins-ci.org/commit/testng-plugin-plugin/eaaa4116e35fe3582997682e3a118108c3545f81 Log: Fixed - JENKINS-16665: showing ± sign when nothing has changed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.
Nalin Makar resolved JENKINS-18498 as Fixed TestNG reports not working on specific build. will be fixed in v1.2 Change By: Nalin Makar (30/Jun/13 12:46 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.
Nalin Makar assigned JENKINS-18498 to Nalin Makar TestNG reports not working on specific build. Change By: Nalin Makar (30/Jun/13 12:46 AM) Assignee: nalin_makar Nalin Makar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-18498) TestNG reports not working on specific build.
SCM/JIRA link daemon commented on JENKINS-18498 TestNG reports not working on specific build. Code changed in jenkins User: Nalin Makar Path: README src/main/java/hudson/plugins/testng/results/BaseResult.java src/main/java/hudson/plugins/testng/results/TestNGResult.java http://jenkins-ci.org/commit/testng-plugin-plugin/8be94c3db0a4305527a25a8d709e91bb9caf2213 Log: Fixed: JENKINS-18498 - hudson.tasks.test.AggregatedTestResultAction$1 cannot be cast to hudson.tasks.test.TestResult This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8423) Slave priority
Pete Tsamouris commented on JENKINS-8423 Slave priority I've been using jenkins for almost a year now, and currently have 12 slaves connected. This is hands down one of the most important upgrades that would greatly affect day to day operations. Oddly enough , my current cross platform build machines consist of a combination of fast-slow-slow, so waiting on a 2-core build when an 8-core machine is idling, kinda looks like squandered resources. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvfb] (JENKINS-18094) Xvfb plugin doesn't write any error message in build log
zregvart commented on JENKINS-18094 Xvfb plugin doesn't write any error message in build log Thank you very much for reporting and testing this bug. I've released 1.0.8 with the fix outlined in comment 4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xvfb] (JENKINS-18094) Xvfb plugin doesn't write any error message in build log
zregvart resolved JENKINS-18094 as Fixed Xvfb plugin doesn't write any error message in build log fixed in 1.0.8 Change By: zregvart (29/Jun/13 9:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519
SCM/JIRA link daemon commented on JENKINS-18415 Can't run shining panda jobs in 1.519 Code changed in jenkins User: Olivier Mansion Path: src/main/java/jenkins/plugins/shiningpanda/interpreters/Virtualenv.java src/main/java/jenkins/plugins/shiningpanda/utils/FilePathUtil.java src/main/java/jenkins/plugins/shiningpanda/workspace/MasterWorkspace.java src/main/java/jenkins/plugins/shiningpanda/workspace/SlaveWorkspace.java src/main/java/jenkins/plugins/shiningpanda/workspace/Workspace.java src/main/resources/jenkins/plugins/shiningpanda/workspace/bootstrap.py src/main/resources/jenkins/plugins/shiningpanda/workspace/virtualenv.py src/main/webapp/scripts/bootstrap.py src/main/webapp/scripts/virtualenv.py src/test/java/jenkins/plugins/shiningpanda/workspace/TestMasterWorkspace.java src/test/java/jenkins/plugins/shiningpanda/workspace/TestSlaveWorkspace.java src/test/java/jenkins/plugins/shiningpanda/workspace/TestWorkspace.java http://jenkins-ci.org/commit/shiningpanda-plugin/e77a484919239bbf3b6e913aa2b1dbde0fa81b64 Log: JENKINS-18415 Can't run shining panda jobs in 1.519 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Martin Buchmayr started work on JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin Change By: Martin Buchmayr (29/Jun/13 6:42 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Martin Buchmayr stopped work on JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin Change By: Martin Buchmayr (29/Jun/13 6:43 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Martin Buchmayr commented on JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin On some files it lists the items, on others it doesn't. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-17959) Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin
Martin Buchmayr updated JENKINS-17959 Unable to view High and Normal Priority Duplicate Code details using Publish Duplicate Code analysis results plugin No files are listed on details page, PHP Depend Change By: Martin Buchmayr (29/Jun/13 6:41 PM) Attachment: nodetails.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Jacob Robertson edited a comment on JENKINS-18386 more flexible job filter by parameter I implemented this, but it's pretty sketchy. Essentially, it will do a toString, and whatever comes back will be matched on. In the examples you gave, they don't actually have a very good toString method, however, it will actually work if you use a flexible enough regex. For example, if the toString returns something like "SomeParam(name=foo, value=bar)", and you want to match on the value "bar", you would have to write a regex that took into account the actual toString, like doing ".*bar.*" or whatever. This will work for the case you described. I forgot the exact toString, but it's something like the example I gave here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Jacob Robertson commented on JENKINS-18386 more flexible job filter by parameter I implemented this, but it's pretty sketchy. Essentially, it will do a toString, and whatever comes back will be matched on. In the examples you gave, they don't actually have a very good toString method, however, it will actually work if you use a flexible enough regex. For example, if the toString returns something like "SomeParam(name=foo, value=bar)", and you want to match on the value "bar", you would have to write a regex that took into account the actual toString, like doing ".bar." or whatever. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Jacob Robertson edited a comment on JENKINS-18386 more flexible job filter by parameter I implemented this, but it's pretty sketchy. Essentially, it will do a toString, and whatever comes back will be matched on. In the examples you gave, they don't actually have a very good toString method, however, it will actually work if you use a flexible enough regex. For example, if the toString returns something like "SomeParam(name=foo, value=bar)", and you want to match on the value "bar", you would have to write a regex that took into account the actual toString, like doing ".*bar.*" or whatever. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Jacob Robertson resolved JENKINS-18386 as Fixed more flexible job filter by parameter Change By: Jacob Robertson (29/Jun/13 6:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18399) possibility to filter jobs by "Restrict where this project can be run"
Jacob Robertson resolved JENKINS-18399 as Fixed possibility to filter jobs by "Restrict where this project can be run" Change By: Jacob Robertson (29/Jun/13 6:29 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-17093) Filter to show N jobs sorted by most recently completed
Jacob Robertson resolved JENKINS-17093 as Fixed Filter to show N jobs sorted by most recently completed Change By: Jacob Robertson (29/Jun/13 6:29 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18399) possibility to filter jobs by "Restrict where this project can be run"
Jacob Robertson commented on JENKINS-18399 possibility to filter jobs by "Restrict where this project can be run" Use the Regular _expression_ filter to filter on the node _expression_. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-17597) Poor performance using ParameterFilter
Jacob Robertson resolved JENKINS-17597 as Fixed Poor performance using ParameterFilter Change By: Jacob Robertson (29/Jun/13 6:29 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
dogfood commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Integrated in jenkins_main_trunk #2675 JENKINS-15846 Deadlock during Maven builds Parsing POM step (Revision 13ae5c793663976587a06d3dca585f7559173efb) JENKINS-15846 add changelog entry (Revision 2995c2869d5bdde84dd83976e5df1b63091acbf0) Result = SUCCESS Olivier Lamy : 13ae5c793663976587a06d3dca585f7559173efb Files : pom.xml core/pom.xml maven-plugin/pom.xml Olivier Lamy : 2995c2869d5bdde84dd83976e5df1b63091acbf0 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519
SCM/JIRA link daemon commented on JENKINS-18415 Can't run shining panda jobs in 1.519 Code changed in jenkins User: Olivier Mansion Path: src/main/java/jenkins/plugins/shiningpanda/workspace/Workspace.java src/main/resources/jenkins/plugins/shiningpanda/workspace/bootstrap.py src/main/resources/jenkins/plugins/shiningpanda/workspace/virtualenv.py src/main/webapp/scripts/bootstrap.py src/main/webapp/scripts/virtualenv.py http://jenkins-ci.org/commit/shiningpanda-plugin/0e320e2273569dc2d67e6993203311a4fc8f4b1b Log: JENKINS-18415: Can't run shining panda jobs in 1.519 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
SCM/JIRA link daemon commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/2995c2869d5bdde84dd83976e5df1b63091acbf0 Log: JENKINS-15846 add changelog entry This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
SCM/JIRA link daemon commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Code changed in jenkins User: Olivier Lamy Path: core/pom.xml maven-plugin/pom.xml pom.xml http://jenkins-ci.org/commit/jenkins/13ae5c793663976587a06d3dca585f7559173efb Log: JENKINS-15846 Deadlock during Maven builds Parsing POM step Do not use anymore shaded version of wagon-http as it we can control commons-logging version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-15624) Rest API for view manipulation
Jacob Robertson assigned JENKINS-15624 to Unassigned Rest API for view manipulation Change By: Jacob Robertson (29/Jun/13 12:01 PM) Assignee: Jacob Robertson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-18453) Need Security\Impersonation Feature for Jenkins Jobs
Vijendra Patil updated JENKINS-18453 Need Security\Impersonation Feature for Jenkins Jobs Change By: Vijendra Patil (29/Jun/13 11:51 AM) Description: Hi,I need to execute few of the Jenkins jobs such as "Release to Production" through Jenkins UI using logged on user credential. The reason is, its the Support Team Members who have access to the production boxes, so in order to deploy any code base to production, all the Windows Deploy Commands (ex, create, update files, folder etc.) needs to be run with specific user credential who has access to the Production Box.I tried using parameterized plugin but couldn't able to pass the Password successfully to the batch file which contains MSDeploy instructions. I checked Role based security plugin, project matrix , active directory etc, but that doesn't help me much. I just need a plugin which should ask for user to provide their credential before start building the Job and should use the user credential to get the job executed, so that my MSDeploy command will be able to deploy the code on Production boxes, when the Support team member build that Job using their credential. I wish there was support for impersonation. Right now all the Jenkins Jobs are getting executed using the service account which the Tomcat service is configured to run with on which Jenkins is hosted.Both Developers and Support team members are ADMIN on both Jenkins web server as well as on Jenkins web application. I am looking forward to the following.=Each job can have a checkbox say "Execute using another user credential". Upon checking that Now when we start the job by clicking on Build button, which is having "Execute using another user credential" checkbox checked, the application should ask to provide credential that needs to be used for Building that Job. That job should get executed then with that particular credential. So even if I can be able to run the job "Release To Production" using my credential then it will not succeed as I don't have access to Production web servers for creating files, folders etc. But when the same job gets executed by Support team, it should succeed as they have access to Production servers for creating files, folders, executing any MSDeploy commands.== Any help would be appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Richard Bywater resolved JENKINS-17386 as Fixed Gradle.properties ignored after 1.22 upgrade Release 1.23 performed to make GRADLE_USER_HOME of workspace an option. Change By: Richard Bywater (29/Jun/13 9:11 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Richard Bywater commented on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade After no objections on the Jenkins mailing list, I have just deployed a 1.23 release with Nicolas' change. There is now an option to use the workspace as the GRADLE_USER_HOME with the default being the old setting which should fix the issue for a number of people. Not sure how long the release takes to show but hopefully won't be long. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible
Torsten Zander
created JENKINS-18553
configuration is lost, and no new configuration possible
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
build-pipeline
Created:
29/Jun/13 8:14 AM
Description:
after updateing the build-pipeline to 1.3.4.1. And jenkins to 1.520 all my pipline configuration are gone. Any new configuration have no affect. On the pipline page there is this error message:
makeStaplerProxy('/$stapler/bound/d3fbd014-3909-4a15-9246-39f5fd687e2e','95e5bbc943cc4cda47bb2806d8975deb',['triggerManualBuild','retryBuild','rerunBuild']), Handlebars.compile(buildCardTemplateSource), Handlebars.compile(projectCardTemplateSource), 3000);
Environment:
ubuntu
Project:
Jenkins
Priority:
Major
Reporter:
Torsten Zander
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12827) api should return the build number that was queued.
Kannan Manickam commented on JENKINS-12827 api should return the build number that was queued. I'm not sure how easy it will be to add this functionality in the Jenkins API itself. As the build number is determined once the build is moved from the queue to one of the executors, it might be hard to return the build number as soon as the build is triggered. I looked around the code in Jenkins and it doesn't seem to be an easy fix. However I have authored a jenkins_api_client ruby gem which makes use of the new behavior of Jenkins' response to build POST requests. In recent versions, jenkins returns a location header to the response of the build POST request. This location header contains the location of the queue item for the particular build. This queue item can be continuously queried until it is placed in one of the executors. Once the queue item reaches an executor, it is assigned with a build number. I have implemented a neat solution here https://github.com/arangamani/jenkins_api_client/issues/88 which will optionally accept an argument on whether to return the build number and return the build number once it is obtained. The only downside is that if there aren't enough idle executors of another build for the same job is running, this call will have to wait until it obtains the build number. Which is why I made this optional so people can decide whether to wait or not. Any comments on my implementation would be appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
SCM/JIRA link daemon commented on JENKINS-18386 more flexible job filter by parameter Code changed in jenkins User: jacob_robertson Path: src/main/webapp/most-recent-help.html src/main/webapp/regex-help.html http://jenkins-ci.org/commit/view-job-filters-plugin/26f950ad6f7a5b599d0f1e859743e3aae92f2530 Log: fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-17093) Filter to show N jobs sorted by most recently completed
SCM/JIRA link daemon commented on JENKINS-17093 Filter to show N jobs sorted by most recently completed Code changed in jenkins User: jacob_robertson Path: src/main/webapp/most-recent-help.html src/main/webapp/regex-help.html http://jenkins-ci.org/commit/view-job-filters-plugin/26f950ad6f7a5b599d0f1e859743e3aae92f2530 Log: fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-17597) Poor performance using ParameterFilter
SCM/JIRA link daemon commented on JENKINS-17597 Poor performance using ParameterFilter Code changed in jenkins User: jacob_robertson Path: src/main/webapp/most-recent-help.html src/main/webapp/regex-help.html http://jenkins-ci.org/commit/view-job-filters-plugin/26f950ad6f7a5b599d0f1e859743e3aae92f2530 Log: fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-18399) possibility to filter jobs by "Restrict where this project can be run"
SCM/JIRA link daemon commented on JENKINS-18399 possibility to filter jobs by "Restrict where this project can be run" Code changed in jenkins User: jacob_robertson Path: src/main/webapp/most-recent-help.html src/main/webapp/regex-help.html http://jenkins-ci.org/commit/view-job-filters-plugin/26f950ad6f7a5b599d0f1e859743e3aae92f2530 Log: fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56]
Peter Loron commented on JENKINS-17883 flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56] Am seeing the same behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
