![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
redsolo
|
|
Components:
|
tfs-plugin |
|
Created:
|
09/Jan/15 8:58 PM
|
|
Description:
|
It looks like pull request 17 in v3.0.0 changed the way it names users detected by changeset from plain userID to domain\userID. This blew up my Jenkins user identities and build emails.
TFS plugin v2.0 looks like it was just getting back the plain username for a changeset, so it was able to build a link to an existing Jenkins user on the changes screen. We're using the Active Directory plugin/strategy for authentication and it creates the Jenkins users as their simple userID and not domain\userid (which we like and which cooperates with our email address structures).
TFS plugin v3.0.0 and later return domain\username, which is perceived as a new, unique user. Emails end up going to that new user account (which isn't a valid email address), and the build changes view's user links are all pointed to the bogus accounts. I rolled back to TFS plugin v2.0 and everything is back to normal now, but our build history is fairly polluted. We'd also love to be able to use the build labeling feature from the latest version.
Please contact me if you need repro help or screenshots or anything else.
|
|
Environment:
|
Windows 7, Windows Server 2012 R2, TFS Server 2012
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
security
windows
user-experience
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jesse Jacob
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
