This repository was archived by the owner on Jan 17, 2024. It is now read-only.
[REVIEW] Make CustomConfigItem backwards compatible#34
Merged
raydouglass merged 1 commit intogpuopenanalytics:masterfrom Jul 30, 2020
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CustomConfigItemwas madeSerializableto accommodate pipeline jobs. It was done by overriding the default serializable methods sinceOptionalis notSerializable. However, this made the class incompatible with previous versions so that after upgrading fro v0.0.3 to v0.0.6, job configs would not properly migrate anyCustomConfigItemconfigurations thus breaking jobs.This migrates the
Optionalfield to a nullable field following Jenkins best practices for maintaining backwards compatibility (https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility).