> On 24.10.2016, at 18:58, Christian McHugh <[email protected]> wrote: > > - add readResolve compatibility code so existing job configs can be read > successfully > I don't know what this means. Do you have an example?
Currently, existing projects will have all the configuration stored in a serialized SaltAPIBuilder. When users upgrade the plugin and load that from disk, they want all their data to still be there, even if you moved things around in code. The solution is to keep all existing fields in SaltAPIBuilder, but making them transient (so they no longer get serialized). Then, add a (private) readResolve method that looks whether values are set on those fields, and if they are, creates ClientInterface instances and moves the values over. https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9002E334-D5E9-4174-B9E4-52A15C591879%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
