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

No mail sent because wrong credentials are used after upgrade to 2.85

XMLWordPrintable

    • 2.86

      After Update email-ext-plugin to 2.85 the credentials are converted but if a mail should send it appears an login error on mail server because it use a different user with password: null value

      see Github comment: https://github.com/jenkinsci/email-ext-plugin/pull/325#issuecomment-974163307

      I try to reproduce it with simple steps the days

          [JENKINS-67220] No mail sent because wrong credentials are used after upgrade to 2.85

          Michael Suhr created issue -

          Alex Earl added a comment -

          I think I can reproduce this, I will work on a solution.

          Alex Earl added a comment - I think I can reproduce this, I will work on a solution.

          Matthias Klein added a comment -

          Also have the same problem after updating the plugin.

          I had to create the credentials again to make them work. The automatically converted ones did not work.

          Matthias Klein added a comment - Also have the same problem after updating the plugin. I had to create the credentials again to make them work. The automatically converted ones did not work.
          Alex Earl made changes -
          Assignee New: Alex Earl [ slide_o_mix ]

          Diego Cerna added a comment -

          I was trying to find a workaround and noticed that the credentials are not used if the scope is set to System, is it expected for them to have a global scope?

          A test with credentials using global scope succeeded

          Diego Cerna added a comment - I was trying to find a workaround and noticed that the credentials are not used if the scope is set to System, is it expected for them to have a global scope? A test with credentials using global scope succeeded

          Alex Earl added a comment -

          System credentials are normally used for things outside of jobs, e.g., background processes like SCM polling and such (at least this is my understanding). The plugin checks global credentials. As for the issue this ticket describes, I believe the problem is that the credentials can't be found during the job for some reason. I am still trying to understand the credentials resolution flow so I can understand why the credentials are not found even though they are there.

          Alex Earl added a comment - System credentials are normally used for things outside of jobs, e.g., background processes like SCM polling and such (at least this is my understanding). The plugin checks global credentials. As for the issue this ticket describes, I believe the problem is that the credentials can't be found during the job for some reason. I am still trying to understand the credentials resolution flow so I can understand why the credentials are not found even though they are there.

          Jonathan added a comment -

          I have the same problem, I had to revert to 2.84 as 2.85 does not read the credentials.

          Jonathan added a comment - I have the same problem, I had to revert to 2.84 as 2.85 does not read the credentials.
          Basil Crow made changes -
          Link New: This issue is duplicated by JENKINS-67282 [ JENKINS-67282 ]

          Basil Crow added a comment -

          Fixed in jenkinsci/email-ext-plugin#332. Released in 2.86.

          Basil Crow added a comment - Fixed in jenkinsci/email-ext-plugin#332 . Released in 2.86 .
          Basil Crow made changes -
          Released As New: 2.86
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            slide_o_mix Alex Earl
            mcmics Michael Suhr
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: