How to best handle configuration errors in a Cloud provider plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How to best handle configuration errors in a Cloud provider plugin

Cameron Esfahani
I've written a Cloud provider plugin.

There are situations where the user can have configured my plugin such that it'll always cause an error.

Invalid credentials for example.

What's the best way to handle this case?  If I throw an exception from my call() implementation or return null, Jenkins will still continue to call my call() routine.

For some error types, like a timeout, that's fine.

But if the user supplies me with invalid credentials, it's never going to work, so I want Jenkins to stop calling call() and report some kind of error.

Can I do this?

Cameron Esfahani
[hidden email]

"Americans are very skilled at creating a custom meaning from something that's mass-produced."

Ann Powers


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3D5BEC3F-D99C-4716-B6E1-C82935483742%40apple.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: How to best handle configuration errors in a Cloud provider plugin

Cameron Esfahani
Any ideas?

Cameron Esfahani
[hidden email]

"There are times in the life of a nation when the only place a decent man can find himself is in prison."



> On Nov 8, 2017, at 5:28 PM, Cameron Esfahani <[hidden email]> wrote:
>
> I've written a Cloud provider plugin.
>
> There are situations where the user can have configured my plugin such that it'll always cause an error.
>
> Invalid credentials for example.
>
> What's the best way to handle this case?  If I throw an exception from my call() implementation or return null, Jenkins will still continue to call my call() routine.
>
> For some error types, like a timeout, that's fine.
>
> But if the user supplies me with invalid credentials, it's never going to work, so I want Jenkins to stop calling call() and report some kind of error.
>
> Can I do this?
>
> Cameron Esfahani
> [hidden email]
>
> "Americans are very skilled at creating a custom meaning from something that's mass-produced."
>
> Ann Powers
>
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3D5BEC3F-D99C-4716-B6E1-C82935483742%40apple.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/EE0637B0-4A97-4E73-BCA2-AD9EFD3BD3A9%40apple.com.
For more options, visit https://groups.google.com/d/optout.