I am attempting to test, and use, the Email-ext plugin for Jenkins, and have set it up according to documentation, including setting the SMTP server to smtp.gmail.com:465
, entering a default email suffix, entering my username,password into the SMTP authentication fields, clicked "Use SSL", ...
I applied changes and saved afterwards, and then come back, and see that Jenkins has hashed my saved password in the password field, as that 8 to 16 character password of mine is not there.
How do I fix this, so that I can get on with fulfilling our business requirements?
UPDATE: I tried these same steps (setting up the email,password,...) with the much simpler email service that email-ext is designed to replace, and get exception instantly; /* here are the results */
The issue turned out to be not the password being saved encrypted, but rather I was using my personal account, which, in accordance to my employer's rules, has two-factor authentication enabled. I got a generic no-reply account from my boss, waited a half hour, used it, and all was good.