[JIRA] (JENKINS-35254) Thresholds to mark build unstable

2016-06-22 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 pavan pothnis commented on  JENKINS-35254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Thresholds to mark build unstable   
 

  
 
 
 
 

 
 It does for current scenario. This was just a suggestion, If I want to mark build as unstable if certain number of test fails. This additional option would help.  Thanks, Pavan  
 

  
 
 
 
 

 
 
 

 
 
 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] [testng-plugin] (JENKINS-35254) Thresholds to mark build unstable

2016-06-01 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35254 
 
 
 
  Thresholds to mark build unstable  
 
 
 
 
 
 
 
 
 

Change By:
 
 pavan pothnis 
 
 
 
 
 
 
 
 
 
 Hi All,I am using TestNg plugin  to  for Publishing the Results in  post  Post  Build Actions and having hard time configuring Thresholds for marking Build Unstable / failed. Reason is pretty simple so Because  as  solution should be, As  of now I can either set threshold mode   1.Number of Tests   / 2. Percentage of Testfor marking build as unstable / failed.Which doesn't  work for my scenario, which is 1.  I have to mark  Mark  build as unstable even single test gets skipped or fails.2.  mark  Mark  build as failed when 100% of test cases fails.But due to threshold mode being common among setting build as unstable / failed ,  I can't have  option using  both the options ie;  100% of tests  Threshold  for marking build as failure and  number  Number  of test cases to marking build as unstable.If this option is provided as an improvement for this plugin we can handle increasing number of test cases every now and then without manually having to go and give the exact number of test cases for each  job as threshold .Hope this addition will be helpful to many using this plugin.Thanks,Pavan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [testng-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-31 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Trying to solve this issue with JENKINS-35254. 
Thanks Tom. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35169 
 
 
 
  Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 pavan pothnis 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [testng-plugin] (JENKINS-35254) Thresholds to mark build unstable

2016-05-31 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35254 
 
 
 
  Thresholds to mark build unstable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Nalin Makar 
 
 
 

Attachments:
 

 TestNGConfigaration.PNG 
 
 
 

Components:
 

 testng-plugin 
 
 
 

Created:
 

 2016/Jun/01 5:04 AM 
 
 
 

Environment:
 

 Windows 7 , Jenkins version 2.6 
 
 
 

Labels:
 

 configuration plugin jenkins 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 pavan pothnis 
 
 
 
 
 
 
 
 
 
 
Hi All, 
I am using TestNg plugin to for Publishing the Results in post Build Actions and having hard time configuring Thresholds for marking Build Unstable / failed. 
Reason is pretty simple so as solution should be, As of now I can either set threshold mode  1.Number of Tests 

[JIRA] [testng-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-30 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35169 
 
 
 
  Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 pavan pothnis 
 
 
 

Attachment:
 
 status.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [testng-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-30 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35169 
 
 
 
  Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 
 
As per Tomas Suggestion, I looked into Publish TestNG plugin configuration (See attached Screenshot). 
The threshold is set to mark build unstable / failure when there is 100 % of test cases fails or gets skipped. 
However, even when we have 11/11 Test cases failed. build status is still shown as Success. 
Thanks, Pavan 
 
 
 
 
 
 
 
 
 

Change By:
 
 pavan pothnis 
 
 
 

Component/s:
 
 testng-plugin 
 
 
 

Component/s:
 
 build-failure-analyzer-plugin 
 
 
 

Attachment:
 
 TestngResult.PNG 
 
 
 

Attachment:
 
 TestNGConfigaration.PNG 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

[JIRA] [build-failure-analyzer-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-30 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis commented on  JENKINS-35169 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 
 
I was under impression that build failure analyzer is supposed analyze the result and show the status. 
If not, could you please let me know what could be the issue for which Jenkins Shows Job Status as Success, even when many test cases have failed. 
Thanks, Pavan  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-failure-analyzer-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-27 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis commented on  JENKINS-35169 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 
 
we have downgraded Jenkins version to 2.5 still no help. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-failure-analyzer-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed

2016-05-27 Thread pavanpoth...@outlook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 pavan pothnis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35169 
 
 
 
  Jenkins "Job status" shows success even if it has many / all test cases failed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tomas Westling 
 
 
 

Attachments:
 

 status.png 
 
 
 

Components:
 

 build-failure-analyzer-plugin 
 
 
 

Created:
 

 2016/May/27 8:52 AM 
 
 
 

Environment:
 

 Windows 7, Chrome 50.0.2661.102, Jenkins 2.5,2.6 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 pavan pothnis 
 
 
 
 
 
 
 
 
 
 
Hi All, 
We recently upgraded Jenkins from 2.1 to 2.6. After which Job Status is always success once the execution is completed. 
For example : if a job as 24 test cases and 24 of them also failed, in dashboard the status is still shown as success. 
Please refer to attached screen shot. 
in which test result clearly says that there are 9 failures out of 30 test cases, but still the job status is showing as success. which was not the case with Previous version of Jenkins 2.1.