> what motivates this change [JENKINS-51390](https://issues.jenkins-ci.org/browse/JENKINS-51390): Jenkins Pipelines which had caught an S3-related exception, or were in the process of propagating it up the call stack, caused lower-level errors when attempting to save the program state, since it was assumed that any `Throwable` was truly serializable.
> how we can ensure that all of our exceptions honor the `Serializable` > contract? Most easily, by running FindBugs, which has a detector warning you when a class implementing `Serializable` has some non`transient` fields of types which do not. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1211#issuecomment-390671661
