Jenkins will take "John Doe", convert it to "john.doe" and try to match against LDAP. So if the git commit message is: Committer: John Doe 19:12:00 It turns out that when using LDAP, Jenkins actually matches against the user name of the git committer. The first answer did put me on the track to a solution, though. _TO_UNKNOWN_USERS=trueĭid not work for me. These JAVA_ARGS can be added in /etc/default/jenkins or /etc/sysconfig/jenkins, depending on your distribution.įrom the OP it's not clear if they use LDAP, but here is some information that solved it for me and that I haven't found anywhere, including the Jenkins JIRA. _TO_USERS_WITHOUT_READ=true: send mail to build culprits associated with a valid Jenkins login even if they would not otherwise have read access to the job. _TO_UNKNOWN_USERS=true: send mail to build culprits even if they do not seem to be associated with a valid Jenkins login. (April10,2017) If the security fix is undesirable in a particular instance, it can be disabled with either or both of the following two system properties: For Example in "Name Surname ", the "Name Surname" part will be the Username jenkins tries to lookup in the Jenkins UserDB, but that combination is not the same identifier that is used in our LDAP and thus, jenkins will not send emails.unless: With this security "fix", Jenkins will try to "guess" the Username from the name before the email address. I am using Jenkins with a Gerrit trigger for newly created Patchsets or published drafts. The problem was (for me): SECURITY-372 (advisory) Emails were sent to addresses not associated with
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |