Add workflow to check compatibility

[gaiksaya]

All the issues linked here confirmed that all plugins have passing gradle assemble and mavenlocal() as their first repository in build.gradle are closed now: opensearch-project/opensearch-devops#114

Description

This change adds a workflow to check the compatibility with all the plugins in opensearch-project. It adds a comment if any component is incompatible. Example: gaiksaya#7 (comment)

Related Issues

opensearch-project/opensearch-devops#114

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/19257/
• CommitID: 420f320

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19267/
• CommitID: e757198
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/19273/
• CommitID: e757198

[gaiksaya]

Hi @nknize This PR is ready for review. Please let me know if it needs any changes. Thanks!

[dblock]

I looked at gaiksaya#7 (comment) and it outputs this.

> Task :test:external-modules:test-delayed-aggs:publishNebulaPublicationToMavenLocal
> Task :test:external-modules:test-delayed-aggs:publishToMavenLocal
> Task :checkCompatibility
Compatible components: [https://github.com/opensearch-project/common-utils]

It tells me what's "incompatible" (I suppose it means it didn't build), but doesn't really give me anything actionable like a log, or a reason. What is one supposed to do when they see an error from this check?

[gaiksaya]

I looked at gaiksaya#7 (comment) and it outputs this.

> Task :test:external-modules:test-delayed-aggs:publishNebulaPublicationToMavenLocal
> Task :test:external-modules:test-delayed-aggs:publishToMavenLocal
> Task :checkCompatibility
Compatible components: [https://github.com/opensearch-project/common-utils]

It tells me what's "incompatible" (I suppose it means it didn't build), but doesn't really give me anything actionable like a log, or a reason. What is one supposed to do when they see an error from this check?

The log or reason can be viewed on the workflow itself: https://github.com/gaiksaya/OpenSearch/actions/runs/5472486309/job/14817298994

Regarding action item, that is next in queue to create GitHub issues in respective component repo once the concerned PR is merged.

[bbarani]

@dblock @gaiksaya @nknize Whats the next steps to get this PR merged?

[nknize]

Whats the next steps to get this PR merged?

I missed this notification sorry for the delay. I'm +1 this PR. It will greatly help me prioritize backports. Thanks @bbarani and @gaiksaya!

[gaiksaya]

Moving forward with this PR.
Will monitor if this change is working as intended. If it is, the next step as stated above will be creating GH issues in all incompatible components repositories when the pull request breaking things is merged in this repository.
Thanks!