Rescue OpenSSL::SSL::SSLError in JiraService
What does this MR do?
Catches OpenSSL::SSL::SSLError
in JiraService.
Are there points in the code the reviewer needs to double check?
So... we probably need specs here, but as we're not doing anything with these exceptions (except logging), there's really no specs to add. This is technically poor error handling.
Why was this MR needed?
We blow up if we run into a OpenSSL::SSL::SSLError
exception when testing the JiraService.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts withmaster
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Edited by username-removed-444214