[JIRA] [jenkins-tag-cloud] (JENKINS-29923) Internal error in Jenkins log
Title: Message Title J John assigned an issue to Unassigned Jenkins / JENKINS-29923 Internal error in Jenkins log Change By: J John Component/s: jenkins-tag-cloud Component/s: m2release-plugin Environment: Linuxhudson-ci2.6.27.19-5-default#1SMP2009-02-2804:40:21+0100x86_64x86_64x86_64GNU/LinuxApacheTomcat/6.0.24 Windows javaversion Jenkins 1. 6.0_21Java(TM)SERuntimeEnvironment(build1.6.0_21-b06)JavaHotSpot(TM)64-BitServerVM(build17.0-b16,mixedmode)Hudsonver.1.376HudsonMavenReleasePlug-inPlug-inv0.6.0 623 Assignee: JamesNord Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [m2release-plugin] (JENKINS-29923) Internal error in Jenkins log
Title: Message Title J John created an issue Jenkins / JENKINS-29923 Internal error in Jenkins log Issue Type: Bug Affects Versions: current Assignee: James Nord Components: m2release-plugin Created: 13/Aug/15 2:06 AM Environment: Linux hudson-ci 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux Apache Tomcat/6.0.24 java version 1.6.0_21 Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode) Hudson ver. 1.376 Hudson Maven Release Plug-in Plug-in v0.6.0 Priority: Major Reporter: J John Settings of perform release: Maven will decide the version Specify SCM login/password
[JIRA] [core] (JENKINS-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Title: Message Title J John commented on JENKINS-23272 Re: java.io.IOException: remote file operation failed remote slave Unable to delete Happened in windows slave java.io.IOException: remote file operation failed: E:\workspace at hudson.remoting.Channel@24473716:apim-jenkins-s1: java.nio.file.DirectoryNotEmptyException: E:\workspace\bin\es at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.deleteContents(FilePath.java:1182) at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1040) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.nio.file.DirectoryNotEmptyException: E:\Rolling-dogfood-bvt-tenant\Portals\Portals.Web\Modules\Portals.Web.Apis\bin\es at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:247) at hudson.FilePath.deleteRecursive(FilePath.java:1202) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.access$1100(FilePath.java:191) at hudson.FilePath$15.invoke(FilePath.java:1185) at hudson.FilePath$15.invoke(FilePath.java:1182) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to apim-jenkins-s1(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at hudson.FilePath.act(FilePath.java:978) ... 13 more
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title J John commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Saw this in windows master/slave. Jenkins ver: 1.608 java.lang.IllegalStateException: Invalid object ID 72 iota=73 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.get(ExportTable.java:324) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:311) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:295) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:254) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to apim-jenkins-s3(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:753) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy49.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.lang.Exception: Object was recently deallocated #72 (ref.0) : [hudson.Launcher$RemoteProcess] Created at Wed Jul 29 12:28:51 PDT 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:93) at hudson.remoting.ExportTable.export(ExportTable.java:299) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Released at Wed Jul 29 12:28:51 PDT 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:376) at hudson.remoting.Channel.unexport(Channel.java:612) at
[JIRA] [build-monitor-plugin] (JENKINS-29706) Show weather information in build monitor
Title: Message Title J John updated an issue Jenkins / JENKINS-29706 Show weather information in build monitor Change By: J John Labels: build-monitor-pluginjenkins WhenIopendashboardinIE9Icanseeonlybackgroundimageandnodatathere.Note Presently , thatthisisnotpermissionproblem(differentmessageappears,ifyoulackpermission buildmonitorshowsthelaststatusofajob.Itwillbegreat to viewthispage) addthe'weather'informationtoshowthetrendofthejobaswell . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-monitor-plugin] (JENKINS-29706) Show weather information in build monitor
Title: Message Title J John updated an issue Jenkins / JENKINS-29706 Show weather information in build monitor Change By: J John Issue Type: Bug NewFeature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-monitor-plugin] (JENKINS-29706) Show weather information in build monitor
Title: Message Title J John created an issue Jenkins / JENKINS-29706 Show weather information in build monitor Issue Type: Bug Assignee: Unassigned Components: build-monitor-plugin Created: 29/Jul/15 7:46 PM Environment: Jenkins 1.576 IE9 Priority: Major Reporter: J John When I open dashboard in IE9 I can see only background image and no data there. Note, that this is not permission problem(different message appears, if you lack permission to view this page). Add Comment
[JIRA] [build-monitor-plugin] (JENKINS-29706) Show weather information in build monitor
Title: Message Title J John updated an issue Jenkins / JENKINS-29706 Show weather information in build monitor Change By: J John Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-monitor-plugin] (JENKINS-29706) Show weather information in build monitor
Title: Message Title J John updated an issue Jenkins / JENKINS-29706 Show weather information in build monitor Change By: J John Environment: Jenkins 1.576 IE9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Title: Message Title J John updated an issue Jenkins / JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Change By: J John Environment: Linux2.6.18-348.12.1.el5RedHatEnterpriseLinuxServerrelease5.9(Tikanga) Windows Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28031) Git plugin using committer rather than author name in Changes log
J John
updated JENKINS-28031
Git plugin using committer rather than author name in Changes log
Change By:
J John
(21/Apr/15 11:04 PM)
Issue Type:
Bug
Improvement
Description:
UsingGitPlugin2.3.4.WhenchoosingGITforsourcecontrolsystemandspecifying
Onusing
the
giturlwithhttpandnousername
environmentvariable${CHANGES}
,
when
the
pluginrunsitsetsthecommitterto
logisshownas
a
differentuserthantheauthorandtheonerunningthejenkinsbuild.
onelineas
Setup:JenkinsbuildwithGit.ExecutingNantbuildscript-thisscripthas
[
exec
committer
commandstocallgitforgitadd.andgitcommit-mBuildNumber--authorsvcClairviaBuildandgitpushoriginFixes
]message
Whenthegitpluginisenabled
Ithinkitshouldbeauthorvscommitter
forthe
repo
namein
the
finalpushcommittotheremoterepoalwaysshowsthewronguserbutwillshowtheauthorastheonespecified
log
.
JenkinsisrunningasaservicewiththesvcClairviaBuilduser.Hereisthecommitmessageontheserver:*MS030441isnotthecommitterwhyisthisshowingup?gitconfigglobal-l=user.name=svcClairviaBuilduser.email=svcclairviabu...@johndoe.comBUILD:8.4.2.0-11795a2a7bae5cBrowsecodesvcClairviaBuildauthored3minutesago**ms030441**committed3minutesago
Priority:
Critical
Trivial
Assignee:
NicolasDeLoof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-28031) Git plugin using committer rather than author name in Changes log
J John created JENKINS-28031 Git plugin using committer rather than author name in Changes log Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 21/Apr/15 11:01 PM Description: Using Git Plugin 2.3.4. When choosing GIT for source control system and specifying the git url with http and no username, when the plugin runs it sets the committer to a different user than the author and the one running the jenkins build. Setup: Jenkins build with Git. Executing Nant build script - this script has exec commands to call git for "git add ." and "git commit -m "Build Number" --author "svcClairviaBuild" and "git push origin Fixes" When the git plugin is enabled for the repo the final "push" commit to the remote repo always shows the wrong user but will show the author as the one specified. Jenkins is running as a service with the "svcClairviaBuild" user. Here is the commit message on the server: *MS030441 is not the committer why is this showing up? git config global -l = user.name=svcClairviaBuild user.email=svcclairviabu...@johndoe.com BUILD:8.4.2.0-1179 5a2a7bae5cBrowse code svcClairviaBuild authored 3 minutes ago *ms030441* committed 3 minutes ago Project: Jenkins Priority: Critical Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [configurationslicing-plugin] (JENKINS-26933) Saving change in 'Configure Slicing Plugin' page causing Form too large exception
J John commented on JENKINS-26933 Saving change in Configure Slicing Plugin page causing Form too large exception +1 java.lang.IllegalStateException: Form too large 42220720 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mstest-plugin] (JENKINS-23531) MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed
J John edited a comment on JENKINS-23531 MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed I am getting the same issue for: Jenkins version 1.608 MsTest Plugin version 0.14. Microsoft (R) Build Engine version 12.0.30723.0 Microsoft .NET Framework, version 4.0.30319.34209 Below is the exception stack trace: MSTest: Processing tests results in file(s) Tests\*.trx MSTest: E:\workspace\Tests\file.trx [MSTEST] XML coverage report file not found: E:\workspace\Tests\mstest-coverage.xml [MSTEST] XML coverage report file not found: E:\workspace\Tests\436745.coveragexml MSTest: E:\workspace\Tests\file.trx [MSTEST] XML coverage report file not found: E:\workspace\Tests\mstest-coverage.xml [MSTEST] XML coverage report file not found: E:\workspace\Tests\216227.coveragexml MSTest: E:\workspace\Tests\file.trx ERROR: Publisher hudson.plugins.mstest.MSTestPublisher aborted due to exception java.io.IOException: remote file operation failed: E:\workspace at hudson.remoting.Channel@4c494212:apim-jenkins-s1: hudson.remoting.ProxyException: java.io.IOException: MSTest: Could not transform the MSTest report. Please report this issue to the plugin author at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.mstest.MSTestPublisher.perform(MSTestPublisher.java:99) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1775) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: hudson.remoting.ProxyException: java.io.IOException: MSTest: Could not transform the MSTest report. Please report this issue to the plugin author at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:66) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to apim-jenkins-s1(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:978) ... 11 more Caused by: hudson.remoting.ProxyException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 2-byte UTF-8 sequence. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.mstest.XslTransformer.transform(XslTransformer.java:51) at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:144) at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:68) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:64) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at
[JIRA] [mstest-plugin] (JENKINS-23531) MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed
J John reopened JENKINS-23531 MSTest Plugin - MSTestPublisher aborted due to exception : Getting an error because # could not be transformed I am getting the same issue for Jenkins version 1.608 and MsTest Plugin 0.14. Below is the exception stack trace: MSTest: Processing tests results in file(s) Tests\*.trx MSTest: E:\workspace\Tests\file.trx [MSTEST] XML coverage report file not found: E:\workspace\Tests\mstest-coverage.xml [MSTEST] XML coverage report file not found: E:\workspace\Tests\436745.coveragexml MSTest: E:\workspace\Tests\file.trx [MSTEST] XML coverage report file not found: E:\workspace\Tests\mstest-coverage.xml [MSTEST] XML coverage report file not found: E:\workspace\Tests\216227.coveragexml MSTest: E:\workspace\Tests\file.trx ERROR: Publisher hudson.plugins.mstest.MSTestPublisher aborted due to exception java.io.IOException: remote file operation failed: E:\workspace at hudson.remoting.Channel@4c494212:apim-jenkins-s1: hudson.remoting.ProxyException: java.io.IOException: MSTest: Could not transform the MSTest report. Please report this issue to the plugin author at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.mstest.MSTestPublisher.perform(MSTestPublisher.java:99) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1775) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: hudson.remoting.ProxyException: java.io.IOException: MSTest: Could not transform the MSTest report. Please report this issue to the plugin author at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:66) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to apim-jenkins-s1(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:978) ... 11 more Caused by: hudson.remoting.ProxyException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 2-byte UTF-8 sequence. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.mstest.XslTransformer.transform(XslTransformer.java:51) at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:144) at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:68) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:64) at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2688) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
[JIRA] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John commented on JENKINS-26186 Last Build Trigger Column does not print author name Awesome. So, we can look forward to a global and local configuration for the column 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/d/optout.
[JIRA] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John commented on JENKINS-26186 Last Build Trigger Column does not print author name Can we have the name appear in the trend column as well. Personally, I like seeing the name vs user icon. For rest, icon looks good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John commented on JENKINS-26186 Last Build Trigger Column does not print author name Any update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
J John commented on JENKINS-25115 Recognize failures indicated by JUnit test result file Does this release also parse mstest result files? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John created JENKINS-26186 Last Build Trigger Column does not print author name Issue Type: Bug Assignee: Baptiste Mathus Attachments: Issue.JPG Components: buildtriggerbadge-plugin Created: 20/Dec/14 6:21 PM Description: Last Build Trigger Column does not print author name in the trigger column as shown in the plugin webpage. Attached screenshot. Environment: Jenkins Version 1.593 Build Trigger Plugin 1.3 Windows Server 2012 Project: Jenkins Labels: buildtriggerplugin Priority: Minor Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24225) Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure
J John edited a comment on JENKINS-24225 Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure Nice feature to have This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25109) Navigating between indication
J John created JENKINS-25109 Navigating between indication Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer Created: 10/Oct/14 7:39 PM Description: A mechanism to step to a previous/next failure or have a sub page in the console output for quick navigation. Environment: build failure analyzer, Project: Jenkins Labels: BFA navigation Priority: Major Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22935) Only one line is highlighted per identifier.
J John commented on JENKINS-22935 Only one line is highlighted per identifier. When can this bug be addressed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22935) Only one line is highlighted per identifier.
J John commented on JENKINS-22935 Only one line is highlighted per identifier. That makes sense. It will be useful if there is a flag to enable repeated highlight for an indication. I need this to identify multiple test failures (out of 600 tests) against a build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24225) Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure
J John commented on JENKINS-24225 Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure Also, it would be great if there is a way to navigate from one error to another in the Console Output 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.
