[JIRA] (JENKINS-39250) Add option to disable automatic user creation in Git plugin

2016-10-28 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39250  
 
 
  Add option to disable automatic user creation in Git plugin   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-39250) Add option to disable automatic user creation in Git plugin

2016-10-25 Thread thefriendlyco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Phillips created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39250  
 
 
  Add option to disable automatic user creation in Git plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Oct/25 6:57 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kevin Phillips  
 

  
 
 
 
 

 
 Currently the Git plugin has this 'weird' behavior where by, when someone navigates to changeset details on the Jenkins dashboard the changeset information is parsed to pull out user information for each commit and if one or more of those users don't have user profiles in Jenkins new ones are created for them on the fly automatically. This automatic behavior has the unfortunate side effect of causing redundant, superfluous user profiles to be created on Jenkins which is confusing at best and fragile at worst. For example, suppose a user logs in to the Jenkins dashboard authenticating via LDAP or AD - they will get a user profile created. Then suppose they commit some changes to Git and their Git client / profile has a slightly different configuration from their LDAP profile (ie: maybe their user name is slightly different). Then when someone browses for those changesets on the Jenkins dashboard a second user profile gets magically created with a very similar name to the first - sometimes with overlapping / duplicated metadata in each. Heaven forbid that the same user then has several different repositories or systems they do work on, each potentially with slightly different user names on them, each of which will produce even more redundant copies of Jenkins users magically behind the scenes. To make matters worse, any other Jenkins plugins that make use of these superfluous user profiles ends up producing different results depending on which user profile they decide to choose for any particular operation. Plugins such as the Claim broken build plugin offer very obvious examples of how this causes no end of confusion. Since this plugin allows the user to select a Jenkins user name from a drop down