[JIRA] (JENKINS-39925) CulpritsRecipientProvider does not populate with all users who committed since the last non-broken build when the current build is successful i.e. emailing on a fixed build

[dylan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dylan Underwood created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39925  
 
 
  CulpritsRecipientProvider does not populate with all users who committed since the last non-broken build when the current build is successful i.e. emailing on a fixed build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 email-ext-recipients-column-plugin  
 
 
Created: 
 2016/Nov/21 11:27 PM  
 
 
Environment: 
 Jenkins ver. 2.19.1, Email Extension Plugin version 2.52, Red Hat Enterprise Linux Server release 6.7, Java 1.8, running Jenkins directly, rpm install, launched via service,  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Dylan Underwood  
 

  
 
 
 
 

 
 Using Jenkins Pipeline I need to email all users who made changes while the build was broken as well as when the build is fixed. The CulpritsRecipientProvider provider seems to claim to have this functionality. But when the build result is successful this list is not populated. It is only populated when the build result is not successful.  $class: 'CulpritsRecipientProvider' - Sends email to the list of users who committed a change since the last non-broken build till now. This list at least always include people who made changes in this build, but if the previous build was a failure it also includes the culprit list from there. In my previous version of Jenkins, 1.658, and Email-Ext version 2.52 in a Freestyle project I was able to set the Triggers to send on Fixed and add the correct recipient list. Is this functionality available in a pipeline job?  
 

  
 
 
 
 

  

[JIRA] [build-flow] (JENKINS-22725) build.workspace always null

[dylan...@gmail.com (JIRA)]

Dylan Meissner
 created  JENKINS-22725


build.workspace always null















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


23/Apr/14 5:15 AM



Description:


The following simple statement always prints null. 

out.println build.workspace

This began happening to existing build-flow jobs when recently upgrading to Jenkins 1.560, and is reproducible when creating new build-flow jobs as well. This functionality is important when the build-flow job is creating artifacts.




Environment:


Jenkins ver. 1.560




Project:


Jenkins



Priority:


Major



Reporter:


Dylan Meissner

























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







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