[JIRA] (JENKINS-40051) Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event

[jesse.ja...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Jacob commented on  JENKINS-40051  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event   
 

  
 
 
 
 

 
 Thanks for doing this so quickly!!  
 

  
 
 
 
 

 
 
 

 
 
 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-40051) Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event

[srheb...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Srivardhan Hebbar resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This event is now tracked with the 1.3.3 build.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40051  
 
 
  Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event   
 

  
 
 
 
 

 
Change By: 
 Srivardhan Hebbar  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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...@googlegroup

[JIRA] (JENKINS-40051) Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event

[jesse.ja...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Jacob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40051  
 
 
  Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Srivardhan Hebbar  
 
 
Components: 
 office-365-connector-plugin  
 
 
Created: 
 2016/Nov/26 5:35 AM  
 
 
Environment: 
 Jenkins 2.33, Windows 2012r2, Java 1.7 64bit, Office 365 Connector 1.3  
 
 
Labels: 
 status build-flow  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Jacob  
 

  
 
 
 
 

 
 I'm tempted to call this major because it misses an important use case of Jenkins, which is to understand when problems are corrected. A variety of negative things worth tracking can cause a build status to transition to unstable, which the plugin alerts about just fine, but you also want to know when those negative things are corrected, which this plugin does not do unless you track every success event. Would you consider aligning this plugin more closely with Jenkins status changes in other plugins, e.g. email-ext (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin)? Email-ext treats the status changes: unstable -> success failure -> success The same way with the "fixed" trigger. I'm not arguing to add another trigger condition to the Office 365 Connector plugin, but just to including UNSTABLE -> SUCCESS status changes to the "Notify Back To Normal" event. Currently only FAILURE -> SUCCESS causes "Notify Back To Normal", which doesn't align well with our use case. When developers generate unstable builds from checking in failing tests or adding code analysis errors, we'd like to know when they've fixed it the same w