[JIRA] (JENKINS-13506) Plugin incompatible to Rhodecode 1.3.4
Matthias Scholz created JENKINS-13506: - Summary: Plugin incompatible to Rhodecode 1.3.4 Key: JENKINS-13506 URL: https://issues.jenkins-ci.org/browse/JENKINS-13506 Project: Jenkins Issue Type: Bug Components: mercurial Affects Versions: current Environment: jenkins 1.458 running on linux rhodecode 1.3.4 ( released: 2012-03-29 ) Reporter: Matthias Scholz Assignee: Kohsuke Kawaguchi URL to revisions, files and diffs are incorrect. Example path to revision: .http://server/group/repository/rev/754894d3e45e should be .http://server/group/group/repository/changeset/754894d3e45ee27f2a5721c4db853d93760d773c Example path to files: .http://server/group/repository/file/754894d3e45e/Makefile should be .http://server/group/group/repository/files/754894d3e45ee27f2a5721c4db853d93760d773c/Makefile Example path to diff: .http://server/group/group/repository/diff/754894d3e45e/Makefile should be ..http://server/group/group/repository/diff/Makefile?diff2=754894d3e45ee27f2a5721c4db853d93760d773cdiff1=4b5318a76d3dfbd4b49828ede51ca5fe80f70419fulldiff=1diff=diff I also notice that some at least one repository group is missing. We have a more hierarchical repository structure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13506) Plugin incompatible to Rhodecode 1.3.4
[ https://issues.jenkins-ci.org/browse/JENKINS-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Scholz resolved JENKINS-13506. --- Fix Version/s: current Resolution: Not A Defect Just used the wrong web template. Changing to rhodecode in the Repository Browser gives the correct results. Sry Plugin incompatible to Rhodecode 1.3.4 -- Key: JENKINS-13506 URL: https://issues.jenkins-ci.org/browse/JENKINS-13506 Project: Jenkins Issue Type: Bug Components: mercurial Affects Versions: current Environment: jenkins 1.458 running on linux rhodecode 1.3.4 ( released: 2012-03-29 ) Reporter: Matthias Scholz Assignee: Kohsuke Kawaguchi Labels: mercurial, plugin Fix For: current URL to revisions, files and diffs are incorrect. Example path to revision: .http://server/group/repository/rev/754894d3e45e should be .http://server/group/group/repository/changeset/754894d3e45ee27f2a5721c4db853d93760d773c Example path to files: .http://server/group/repository/file/754894d3e45e/Makefile should be .http://server/group/group/repository/files/754894d3e45ee27f2a5721c4db853d93760d773c/Makefile Example path to diff: .http://server/group/group/repository/diff/754894d3e45e/Makefile should be ..http://server/group/group/repository/diff/Makefile?diff2=754894d3e45ee27f2a5721c4db853d93760d773cdiff1=4b5318a76d3dfbd4b49828ede51ca5fe80f70419fulldiff=1diff=diff I also notice that some at least one repository group is missing. We have a more hierarchical repository structure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13036) Boost-Test parsing
[
https://issues.jenkins-ci.org/browse/JENKINS-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160399#comment-160399
]
Matthias Scholz commented on JENKINS-13036:
---
Got the logger working now. Using just: XUnitService as logger entry.
It looks like the BuildInfo section is invalid.
Error:
WARNUNG: [xUnit] - At line 1 of
file:/daten/entwicklung/opt/jenkins/jobs/Test_xunit/workspace/ARTSystemNG_test_log.xml:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'BuildInfo'. One of
'{TestSuite}' is expected.
Test file extraction:
?xml version=1.0 encoding=UTF-8?
TestLog
BuildInfo platform=linux compiler=GNU C++ version 4.5.3 stl=GNU
libstdc++ version 20110428 boost=1.46.1/
TestSuite ...
...
/TestSuite
/TestLog
Boost-Test parsing
--
Key: JENKINS-13036
URL: https://issues.jenkins-ci.org/browse/JENKINS-13036
Project: Jenkins
Issue Type: Bug
Components: xunit
Affects Versions: current
Environment: linux kernel 3.2.1
boost 1.46
jenkins 1.454
xunit plugin 1.40
Reporter: Matthias Scholz
Assignee: gbois
Priority: Critical
Labels: plugin
Attachments: test.xml
Hello,
I am trying to connect ourg UnitTest system with Jenkins using xunit plugin.
The boost xml file is generated by using the following command-line
parameters:
--log_level=all --output_format=XML --report_level=no
Giving the output to jenkins gives:
... .xml' for the metric 'BoostTest' is not valid. The result file has been
skipped.
Is there any possibility to validate against the Boost-Test xsd manually? To
investigate the problem. I searched for a XSD file but could not find any
file nor reference.
I also tried to find some uUnit output using the Logger mechanism. The
description on the plugin website does not work
and also did not look as it could work because the build-in help tells a
different syntax. So I tried several Logger like (setting priority to 'all'):
com.thalesgroup.hudson.plugins.xunit.service.XUnitService
com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer
com.thalesgroup.hudson.plugins.xunit.service.XUnitValidationService
com.thalesgroup.hudson.plugins.xunit.service.XUnitReportProcessorService
com.thalesgroup.hudson.plugins.xunit.service.XUnitLog
xUnit
But the xUnit Logger stayed empty.
So sadly I could not provide any debug information, despite the log file.
Regards,
Matthias Scholz
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13036) Boost-Test parsing
[
https://issues.jenkins-ci.org/browse/JENKINS-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160399#comment-160399
]
Matthias Scholz edited comment on JENKINS-13036 at 3/19/12 1:27 PM:
Got the logger working now. Using just: XUnitService as logger entry.
It looks like the BuildInfo section is invalid.
Error:
WARNUNG: [xUnit] - At line 1 of
file:/.../Test_xunit/workspace/ARTSystemNG_test_log.xml:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'BuildInfo'. One of
'{TestSuite}' is expected.
Test file extraction:
?xml version=1.0 encoding=UTF-8?
TestLog
BuildInfo platform=linux compiler=GNU C++ version 4.5.3 stl=GNU
libstdc++ version 20110428 boost=1.46.1/
TestSuite ...
...
/TestSuite
/TestLog
was (Author: matthiasscholz):
Got the logger working now. Using just: XUnitService as logger entry.
It looks like the BuildInfo section is invalid.
Error:
WARNUNG: [xUnit] - At line 1 of
file:/daten/entwicklung/opt/jenkins/jobs/Test_xunit/workspace/ARTSystemNG_test_log.xml:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'BuildInfo'. One of
'{TestSuite}' is expected.
Test file extraction:
?xml version=1.0 encoding=UTF-8?
TestLog
BuildInfo platform=linux compiler=GNU C++ version 4.5.3 stl=GNU
libstdc++ version 20110428 boost=1.46.1/
TestSuite ...
...
/TestSuite
/TestLog
Boost-Test parsing
--
Key: JENKINS-13036
URL: https://issues.jenkins-ci.org/browse/JENKINS-13036
Project: Jenkins
Issue Type: Bug
Components: xunit
Affects Versions: current
Environment: linux kernel 3.2.1
boost 1.46
jenkins 1.454
xunit plugin 1.40
Reporter: Matthias Scholz
Assignee: gbois
Priority: Critical
Labels: plugin
Attachments: test.xml
Hello,
I am trying to connect ourg UnitTest system with Jenkins using xunit plugin.
The boost xml file is generated by using the following command-line
parameters:
--log_level=all --output_format=XML --report_level=no
Giving the output to jenkins gives:
... .xml' for the metric 'BoostTest' is not valid. The result file has been
skipped.
Is there any possibility to validate against the Boost-Test xsd manually? To
investigate the problem. I searched for a XSD file but could not find any
file nor reference.
I also tried to find some uUnit output using the Logger mechanism. The
description on the plugin website does not work
and also did not look as it could work because the build-in help tells a
different syntax. So I tried several Logger like (setting priority to 'all'):
com.thalesgroup.hudson.plugins.xunit.service.XUnitService
com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer
com.thalesgroup.hudson.plugins.xunit.service.XUnitValidationService
com.thalesgroup.hudson.plugins.xunit.service.XUnitReportProcessorService
com.thalesgroup.hudson.plugins.xunit.service.XUnitLog
xUnit
But the xUnit Logger stayed empty.
So sadly I could not provide any debug information, despite the log file.
Regards,
Matthias Scholz
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13036) Boost-Test parsing
[ https://issues.jenkins-ci.org/browse/JENKINS-13036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Scholz updated JENKINS-13036: -- Issue Type: Improvement (was: Bug) Priority: Minor (was: Critical) Boost-Test parsing -- Key: JENKINS-13036 URL: https://issues.jenkins-ci.org/browse/JENKINS-13036 Project: Jenkins Issue Type: Improvement Components: xunit Affects Versions: current Environment: linux kernel 3.2.1 boost 1.46 jenkins 1.454 xunit plugin 1.40 Reporter: Matthias Scholz Assignee: gbois Priority: Minor Labels: plugin Attachments: test.xml Hello, I am trying to connect ourg UnitTest system with Jenkins using xunit plugin. The boost xml file is generated by using the following command-line parameters: --log_level=all --output_format=XML --report_level=no Giving the output to jenkins gives: ... .xml' for the metric 'BoostTest' is not valid. The result file has been skipped. Is there any possibility to validate against the Boost-Test xsd manually? To investigate the problem. I searched for a XSD file but could not find any file nor reference. I also tried to find some uUnit output using the Logger mechanism. The description on the plugin website does not work and also did not look as it could work because the build-in help tells a different syntax. So I tried several Logger like (setting priority to 'all'): com.thalesgroup.hudson.plugins.xunit.service.XUnitService com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer com.thalesgroup.hudson.plugins.xunit.service.XUnitValidationService com.thalesgroup.hudson.plugins.xunit.service.XUnitReportProcessorService com.thalesgroup.hudson.plugins.xunit.service.XUnitLog xUnit But the xUnit Logger stayed empty. So sadly I could not provide any debug information, despite the log file. Regards, Matthias Scholz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13036) Boost-Test parsing
Matthias Scholz created JENKINS-13036: - Summary: Boost-Test parsing Key: JENKINS-13036 URL: https://issues.jenkins-ci.org/browse/JENKINS-13036 Project: Jenkins Issue Type: Bug Components: xunit Affects Versions: current Environment: linux kernel 3.2.1 boost 1.46 jenkins 1.454 xunit plugin 1.40 Reporter: Matthias Scholz Assignee: gbois Priority: Critical Attachments: test.xml Hello, I am trying to connect ourg UnitTest system with Jenkins using xunit plugin. The boost xml file is generated by using the following command-line parameters: --log_level=all --output_format=XML --report_level=no Giving the output to jenkins gives: ... .xml' for the metric 'BoostTest' is not valid. The result file has been skipped. Is there any possibility to validate against the Boost-Test xsd manually? To investigate the problem. I searched for a XSD file but could not find any file nor reference. I also tried to find some uUnit output using the Logger mechanism. The description on the plugin website does not work and also did not look as it could work because the build-in help tells a different syntax. So I tried several Logger like (setting priority to 'all'): com.thalesgroup.hudson.plugins.xunit.service.XUnitService com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer com.thalesgroup.hudson.plugins.xunit.service.XUnitValidationService com.thalesgroup.hudson.plugins.xunit.service.XUnitReportProcessorService com.thalesgroup.hudson.plugins.xunit.service.XUnitLog xUnit But the xUnit Logger stayed empty. So sadly I could not provide any debug information, despite the log file. Regards, Matthias Scholz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
