[JIRA] (JENKINS-13844) "Emulate clean checkout by..." does not work with 1.7 subversion repositories
Martin Adam commented on JENKINS-13844 "Emulate clean checkout by..." does not work with 1.7 subversion repositories Does this explain not deleting unversioned files as well? Because you're mentioning only ignored 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
[JIRA] (JENKINS-13844) "Emulate clean checkout by..." does not work with 1.7 subversion repositories
Martin Adam commented on JENKINS-13844 "Emulate clean checkout by..." does not work with 1.7 subversion repositories same here, environmen same as in comment above me, only I have jenkins 1.475 and it's a master building node This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5264) no FxCop report may mean no warnings to display
Martin Adam commented on JENKINS-5264 no FxCop report may mean no warnings to display but it may also indicate that the fxCop failed/crashed, that's why I think current behavior is correct you can easily force fxCop to generate empty file with /fo switch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12792) Violation Plugin display [no report] for FxCop
Martin Adam edited a comment on JENKINS-12792 Violation Plugin display [no report] for FxCop to the original description: you can force fxCop to generate file even with no messages (/fo switch), it could solve your problem (but I haven't tried that) to alexlombardi: I don't think your situation is really related to this bug - situation you are describing was working correctly with older jenkins. I've upgraded jenkins last week (had about 6 month old version before) and only then the messages near the exclamation mark dissapeared - so I'm quite sure that's another problem and it's most likely caused by some change in jenkins itself EDIT: see JENKINS-12764 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12764) Missing Overview in Violations Plugin
Martin Adam commented on JENKINS-12764 Missing Overview in Violations Plugin Don't want to be offensive, but is this really minor? you cannot see the fx cop messages AT ALL in many cases (and in the rest you see only description of the problem, not the problem itself, so almost the same..) To me it sounds more like critical - we had to switch to warnings plugin in our company cause of that... (which unfortunatelly doesn't have all the things violations plugin has) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12792) Violation Plugin display [no report] for FxCop
Martin Adam commented on JENKINS-12792 Violation Plugin display [no report] for FxCop to the original description: you can force fxCop to generate file even with no messages (/fo switch), it could solve your problem (but I haven't tried that) to alexlombardi: I don't think your situation is really related to this bug - situation you are describing was working correctly with older jenkins. I've upgraded jenkins last week (had about 6 month old version before) and only then the messages near the exclamation mark dissapeared - so I'm quite sure that's another problem and it's most likely caused by some change in jenkins itself This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14190) Wrong autocompletion of node names with spaces
Martin Adam created JENKINS-14190 Wrong autocompletion of node names with spaces Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: auto_complete_1.jpg, auto_complete_2.jpg, auto_complete_3.jpg Components: core Created: 22/Jun/12 7:36 AM Description: Auto-complete is working wrong on nodes whith spaces in names. Or maybe it's just not compatible with the project configuration field "Restrict where this project can be run"; as this field expects the node name to be sourrounded by quotes see screenshots (on 3d one I've added the quotes manually) Project: Jenkins Priority: Trivial Reporter: Martin Adam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14172) [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings
Martin Adam edited a comment on JENKINS-14172 [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings As I mentioned in the description, I get the same error even when parsing XML output from FxCop [WARNINGS] Parsing warnings in files 'fxcop-result.xml' with parser FxCop [WARNINGS] Parsing 1 files in C:_hudson\jobs\Framework\workspace [WARNINGS] Parsing of file C:_hudson\jobs\Framework\workspace\fxcop-result.xml failed due to an exception: hudson.util.IOException2: Content is not allowed in prolog. . (The same output file is parsed by Violation plugin without errors) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14172) [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings
Martin Adam commented on JENKINS-14172 [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings As I mentioned in the description, I get the same error even when parsing XML output from FxCop [WARNINGS] Parsing warnings in files 'fxcop-result.xml' with parser FxCop [WARNINGS] Parsing 1 files in C:_hudson\jobs\Framework\workspace [WARNINGS] Parsing of file C:_hudson\jobs\Framework\workspace\fxcop-result.xml failed due to an exception: hudson.util.IOException2: Content is not allowed in prolog. . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14170) [Warnings] FxCopParser NotSerializableException when executing job on remote node
Martin Adam commented on JENKINS-14170 [Warnings] FxCopParser NotSerializableException when executing job on remote node I thought so, but still, it is strange, that Violation plugin has no problem with running the FxCop parsenr on a remote node This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14172) [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings
Martin Adam created JENKINS-14172 [Warnings] Content is not allowed in prolog exception when parsing FxCop warnings Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 21/Jun/12 7:19 AM Description: When parsing fxCop results (fxcop 1.35), I get following error (see lower). The same file is parsed by Violation plugin without errors. note: when the fxCop results are parsed from console, it caused the whole build process to fail, when the results are parsed from an fxCop_output.xml, the build finishes correctly and this error is just a warning in cosole output I can provide the fxCop output, but rather not publicly... [WARNINGS] Parsing warnings in console log with parser FxCop ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception hudson.util.IOException2: Content is not allowed in prolog. at hudson.plugins.violations.types.fxcop.FxCopParser.parse(FxCopParser.java:57) at hudson.plugins.warnings.parser.ViolationsAdapter.parse(ViolationsAdapter.java:60) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:321) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:300) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:286) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:234) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1485) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at hudson.plugins.violations.types.fxcop.FxCopParser.parse(FxCopParser.java:45) Project: Jenkins Priority: Major Reporter: Martin Adam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14170) [Warnings] FxCopParser NotSerializableException when executing job on remote node
Martin Adam created JENKINS-14170 [Warnings] FxCopParser NotSerializableException when executing job on remote node Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 21/Jun/12 6:56 AM Description: When my job is running on a remote node (Windows) I got this error when trying to parse fxcop with Warnings plugin [WARNINGS] Parsing warnings in files 'fxcop-result.xml' with parser FxCop ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: c:_hudson\jobs@node2\workspace\ProjectName at hudson.remoting.Channel@1d3dc59:node2 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:320) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:233) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1485) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@127db28 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:645) at hudson.FilePath.act(FilePath.java:831) ... 13 more Caused by: java.io.NotSerializableException: hudson.plugins.violations.types.fxcop.FxCopParser at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.writeObject(Unknown Source) at java.util.ArrayList.writeObject(Unknown Source) at sun.reflect.GeneratedMethodAccessor423.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at java.io.ObjectStreamClass.invokeWriteObject(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source) at java.io.ObjectOutputStream.writeSerialData(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source) at java.io.ObjectOutputStream.writeObject0(Unknown Source) at java.io.ObjectOutputStream.writeObject(Unknown Source) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) ... 16 more Project: Jenkins
