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
di...@apple.com

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

Ann Powers

[Cameron Esfahani]

Any ideas?

Cameron Esfahani
di...@apple.com

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

> --
> 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 jenkinsci-de...@googlegroups.com.
> 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.