Skip to content

Remove compatibility checker#12971

Merged
dblock merged 1 commit intoopensearch-project:mainfrom
peternied:remove-compatibility-tests
Apr 16, 2024
Merged

Remove compatibility checker#12971
dblock merged 1 commit intoopensearch-project:mainfrom
peternied:remove-compatibility-tests

Conversation

@peternied
Copy link
Copy Markdown
Member

@peternied peternied commented Mar 28, 2024

Description

I do not see much value in continuing to run the compatibility checker. The workflow adds additional comments and test results that are ignored even when they detect downstream failures.

Related Issues

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Peter Nied <petern@amazon.com>
@github-actions github-actions bot added Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. enhancement Enhancement or improvement to existing feature or request RFC Issues requesting major changes labels Mar 28, 2024
@github-actions

This comment was marked as resolved.

@github-actions

This comment was marked as resolved.

@codecov

This comment was marked as resolved.

Copy link
Copy Markdown
Member

@dblock dblock left a comment

Choose a reason for hiding this comment

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

It doesn't look like there are any comments one way or another on the RFC. Can we please solicit at least some input? I'll add mine.

@peternied
Copy link
Copy Markdown
Member Author

@dblock Isn't this PR a way to solicit additional feedback on the topic? 😉

@peternied
Copy link
Copy Markdown
Member Author

@dblock Since we've added the Java API compatibility check [1], I think this workflow's purpose has been replaced with a more reliable process. What do you think about removing this less reliable and often ignored check?

@github-actions github-actions bot added the discuss Issues intended to help drive brainstorming and decision making label Apr 15, 2024
@kotwanikunal
Copy link
Copy Markdown
Member

+1. I was going through another PR today and I think the new mechanism serves its purpose well

@dblock dblock merged commit a2f07ed into opensearch-project:main Apr 16, 2024
@dblock dblock added the backport 2.x Backport to 2.x branch label Apr 16, 2024
@peternied peternied deleted the remove-compatibility-tests branch April 16, 2024 13:01
@opensearch-trigger-bot

This comment was marked as resolved.

peternied added a commit to peternied/OpenSearch-1 that referenced this pull request Apr 16, 2024
Signed-off-by: Peter Nied <petern@amazon.com>
(cherry picked from commit a2f07ed)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 2.x Backport to 2.x branch Build Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement. discuss Issues intended to help drive brainstorming and decision making enhancement Enhancement or improvement to existing feature or request RFC Issues requesting major changes skip-changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[RFC] How helpful is the compatibility checker

4 participants