Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement plugin data versioning #390

Merged

Conversation

nikita-tkachenko-datadog
Copy link
Collaborator

@nikita-tkachenko-datadog nikita-tkachenko-datadog commented Feb 1, 2024

Requirements for Contributing to this repository

  • Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
  • The pull request must only fix one issue at the time.
  • The pull request must update the test suite to demonstrate the changed functionality.
  • After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?

Implements versioning mechanism for plugin data that is serialized to disk.

This helps to avoid deserializing data written by older versions of the plugin in a format that we do not support anymore (currently trying to do so may result in deserializing builds partially - as the result some of the data is not displayed properly in Jenkins UI).

Also, going forward it will be easy to change the data format by adding new converter versions (while ensuring the data written by older versions remains readable).

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

  • Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
  • PR title must be written as a CHANGELOG entry (see why)
  • Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
  • PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
  • PR should not have do-not-merge/ label attached.
  • If Applicable, issue must have kind/ and severity/ labels attached at least.

@nikita-tkachenko-datadog nikita-tkachenko-datadog added the changelog/Fixed Fixed features results into a bug fix version bump label Feb 1, 2024
drodriguezhdez
drodriguezhdez previously approved these changes Feb 2, 2024
Copy link
Collaborator

@drodriguezhdez drodriguezhdez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped nit comments.

return GitCommitAction.class == type;
public static final class ConverterV1 extends VersionedConverter<GitCommitAction> {
public ConverterV1() {
super(1);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: super(1) can be a constant to avoid magic numbers super(VERSION)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, added constants

String versionString = reader.getAttribute(VERSION_ATTRIBUTE);
if (versionString == null) {
// no attribute, data was written by an old version of the plugin
return null;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we're checking null every time we get an action, right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, these checks already exist: even before adding these changes it was possible to get a null simply because an action was never added to a run/node (e.g. if CI Visibility was enabled while the run was already in progress, or if whitelist of tracked jobs changed, etc)

@nikita-tkachenko-datadog nikita-tkachenko-datadog merged commit 250a3c5 into master Feb 2, 2024
16 checks passed
@nikita-tkachenko-datadog nikita-tkachenko-datadog deleted the nikita-tkachenko/plugin-data-versioning branch February 2, 2024 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/Fixed Fixed features results into a bug fix version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

All classic jobs in jenkins turn into failed on datadog plugin v6.0.0
2 participants