[JIRA] (JENKINS-43007) Missing update of plugin description

2017-03-21 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43007  
 
 
  Missing update of plugin description   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2017/Mar/21 10:46 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joe Merten  
 

  
 
 
 
 

 
 I'd released a new version 0.5.0 of AnsiColor plugin 2 day ago. Now, when I navigate to Manage Jenkins → Manage Plugins → Available → AnsiColor is displayed with 0.5.0 → so far so good. But when clicking AnsiColor which is a link to https://plugins.jenkins.io/ansicolor, it displays old information: 0.4.3 https://cloud.githubusercontent.com/assets/6552470/24101793/f0001fee-0d79-11e7-99be-555342ad3c42.png However, when checking https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin a saw a different styled wiki page which shows correct AnsiColor 0.5.0. https://cloud.githubusercontent.com/assets/6552470/24102456/548e6162-0d7c-11e7-95bb-5c79d3d84d82.png How to put them both in sync? See also AnsiColor #99    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-41095) For Unittest++ xml, want to have a tag inside of the tag

2017-03-18 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten edited a comment on  JENKINS-41095  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For Unittest++ xml, want to have a  tag inside of the  tag   
 

  
 
 
 
 

 
 Seems that this just needs a change in [unittest-1.1-to-junit-1.0.xsl|[https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/unittest-1.1-to-junit-1.0.xsl] , ] ,  isn't it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41095) For Unittest++ xml, want to have a tag inside of the tag

2017-03-18 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten edited a comment on  JENKINS-41095  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For Unittest++ xml, want to have a  tag inside of the  tag   
 

  
 
 
 
 

 
 Seems that this just needs a change in [unittest-1.1-to-junit-1.0.xsl|[https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/unittest-1.1-to-junit-1.0.xsl],] isn't it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41095) For Unittest++ xml, want to have a tag inside of the tag

2017-03-18 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten commented on  JENKINS-41095  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For Unittest++ xml, want to have a  tag inside of the  tag   
 

  
 
 
 
 

 
 Seems that this just needs a change in [unittest-1.1-to-junit-1.0.xsl|https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/unittest-1.1-to-junit-1.0.xsl,] isn't it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41093) For Unittest++ xml, only the first failure of each test case is recognized

2017-01-15 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten commented on  JENKINS-41093  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For Unittest++ xml, only the first failure of each test case is recognized   
 

  
 
 
 
 

 
 Ok, now seeing at #JENKINS-11217, Gregory Boissinot wrote:  Can't fix it. A limitation of JUnit capabilities. It's a Jenkins JUnit core issue. But might xUnit merge them together before passing to JUnit core?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41093) For Unittest++ xml, only the first failure of each test case is recognized

2017-01-15 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten edited a comment on  JENKINS-41093  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: For Unittest++ xml, only the first failure of each test case is recognized   
 

  
 
 
 
 

 
 Ok, now seeing at #JENKINS-11217, Gregory Boissinot wrote:  {quote} Can't fix it. A limitation of JUnit capabilities.It's a Jenkins JUnit core issue. {quote} But might xUnit merge them together before passing to JUnit core?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41095) For Unittest++ xml, want to have a tag inside of the tag

2017-01-15 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41095  
 
 
  For Unittest++ xml, want to have a  tag inside of the  tag   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Gregory Boissinot  
 
 
Components: 
 xunit-plugin  
 
 
Created: 
 2017/Jan/16 12:35 AM  
 
 
Environment: 
 Jenkins 1.653, Linux  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joe Merten  
 

  
 
 
 
 

 
 For passing the test duration time to xUnit, it needs to be as an attribute of the  tag like this: 

 

"1.0"?>

  "Package.Suite" name="Testname" time="1.234"/>

 

 It would be nice to alternatively allow to pass this information in a  tag like this: 

 

"1.0"?>

  "Package.Suite" name="Testname">
1.234
  

 

 (It's a bit similar to qt xml format, which uses something like ``; seen here: https://github.com/jenkinsci/xunit-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase2/input.xml) The reason for this improvement request is as follows: I use Unittest++ and Jenkins / xUnit for unit testing on very resource limited bare-metal microcontroller systems. These target systems especially have very low amount of RAM. As long as I have to pass the test duration time as attribute of the  tag, I have to store all the  and  output / content into 

[JIRA] (JENKINS-41094) For Unittest++ xml, only the content of the first tag of each test case is recognized

2017-01-15 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41094  
 
 
  For Unittest++ xml, only the content of the first  tag of each test case is recognized   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Gregory Boissinot  
 
 
Components: 
 xunit-plugin  
 
 
Created: 
 2017/Jan/16 12:16 AM  
 
 
Environment: 
 Jenkins 1.653, Linux  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joe Merten  
 

  
 
 
 
 

 
 For this example xml: 

 

"1.0"?>

  "Package.Suite" name="Testname">
Some output at the beginning of the test
"Path/Filename.cxx(1) : Failed for some reason"/>
Some output at the end of the test
  

 

 the xUnit plugin shows only the content of the first  tag. The content of the second  tag "Some output at the end of the test" is not displayed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[JIRA] (JENKINS-41093) For Unittest++ xml, only the first failure of each test case is recognized

2017-01-15 Thread jenk...@jme.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Merten created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41093  
 
 
  For Unittest++ xml, only the first failure of each test case is recognized   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Gregory Boissinot  
 
 
Components: 
 xunit-plugin  
 
 
Created: 
 2017/Jan/16 12:10 AM  
 
 
Environment: 
 Jenkins 1.653, Linux  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Joe Merten  
 

  
 
 
 
 

 
 For this example xml: 

 

"1.0"?>

  "Package.Suite" name="Testname">
"Path/Filename.cxx(1) : Failed A"/>
"Path/Filename.cxx(2) : Failed B"/>
"Path/Filename.cxx(3) : Failed C"/>
  

 

 the xUnit plugin shows only the first failure "Failed A" in the web UI. The 2nd and 3rd failures ("Failed B" and "Failed C") were not displayed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment