Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16765

Setting an empty email address in User configuration is not saved

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • mailer-plugin
    • master: CentOS 5.8

      I want to disable emails to a particular (automated) user. To do this, I think I can set the user's email address to an empty value.

      In the User's configuration, I can set the email address to an empty value and press Save, the Save appears to succeed, but the empty value is not saved. Opening the User's configuration again shows the full email address (username@domain). In the User's configuration, if I set the address to an empty value and press Apply, I get an empty error window.

      In the System Configuration E-mail section, I have a default domain set. If I remove the default domain, I can set the user's email address to an empty value.

      Since Jenkins does not allow me to set an empty email address when the default email domain is set, I would like the ability to somehow disable Jenkins emails for a particular user.

          [JENKINS-16765] Setting an empty email address in User configuration is not saved

          evernat added a comment - - edited

          Reproduced somewhat using Jenkins 1.549.

          For me, the empty email value is saved.
          But, if there is a default email domain in the global configuration, then opening the user's config page shows that the email of the user is dynamically computed as username@defaultdomain.
          This could be said as a feature and not a bug: it is the goal of the default mail domain to automatically compute user's email based on the username.

          So there seems to be no way in Jenkins 1.549 to remove the email of a user, when there is a default email domain.
          And that should be a request for enhancement.

          evernat added a comment - - edited Reproduced somewhat using Jenkins 1.549. For me, the empty email value is saved. But, if there is a default email domain in the global configuration, then opening the user's config page shows that the email of the user is dynamically computed as username@defaultdomain. This could be said as a feature and not a bug: it is the goal of the default mail domain to automatically compute user's email based on the username. So there seems to be no way in Jenkins 1.549 to remove the email of a user, when there is a default email domain. And that should be a request for enhancement.

          Daniel Beck added a comment -

          Jenkins does not distinguish between users with no email address specified (the default), and users with empty email address specified (your configuration). It tries to infer the email address, and the default suffix is an easy way to do this.

          Not sure this is a bug, as you're basically telling Jenkins "If a user has no email address, as a last resort, use the default suffix" – and it does.

          Daniel Beck added a comment - Jenkins does not distinguish between users with no email address specified (the default), and users with empty email address specified (your configuration). It tries to infer the email address, and the default suffix is an easy way to do this. Not sure this is a bug, as you're basically telling Jenkins "If a user has no email address, as a last resort, use the default suffix" – and it does.

          Dave Bacher added a comment -

          Changed type from Bug to Improvement

          Dave Bacher added a comment - Changed type from Bug to Improvement

            Unassigned Unassigned
            dbacher Dave Bacher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: