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

Adding support to run BWC tests for nightly and release builds #1150

Closed
wants to merge 2 commits into from

Conversation

saratvemulapalli
Copy link
Member

Signed-off-by: Sarat Vemulapalli vemulapallisarat@gmail.com

Description

Adding support to run BWC tests for nightly and release builds via test pipeline.
Refer to: opensearch-project/opensearch-build#90

Issues Resolved

opensearch-project/opensearch-build#296

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

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: Sarat Vemulapalli <vemulapallisarat@gmail.com>
@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 74f7ddd

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 74f7ddd

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 74f7ddd

Copy link
Collaborator

@VachaShah VachaShah left a comment

Choose a reason for hiding this comment

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

LGTM, thank you @saratvemulapalli for the change!

@saratvemulapalli
Copy link
Member Author

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 74f7ddd
Log 421

Reports 421

@saratvemulapalli
Copy link
Member Author

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 74f7ddd
Log 424

Reports 424

@saratvemulapalli
Copy link
Member Author

Some how bwc checks are failing

* What went wrong:
Execution failed for task ':distribution:bwc:minor:buildBwcLinuxTar'.
> Building 1.0.0 didn't generate expected file /var/CITOOL/workflow/OpenSearch_CI/PR_Checks/Gradle_Check/search/distribution/bwc/minor/build/bwc/checkout-1.0/distribution/archives/linux-tar/build/distributions/opensearch-1.0.0-SNAPSHOT-linux-x64.tar.gz

@tlfeng
Copy link
Collaborator

tlfeng commented Aug 26, 2021

start gradle check

@tlfeng
Copy link
Collaborator

tlfeng commented Aug 26, 2021

See more detail of the BWC test failure: #1158

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 74f7ddd
Log 434

Reports 434

@tlfeng
Copy link
Collaborator

tlfeng commented Aug 30, 2021

Hey Sarat, in my PR, the gradle check passed after I merged the current main branch to my branch (#1153 (comment)), so you could try the same.

@saratvemulapalli
Copy link
Member Author

Hey Sarat, in my PR, the gradle check passed after I merged the current main branch to my branch (#1153 (comment)), so you could try the same.

Thanks Tianli!
I left the PR open because the runner is not merged yet. But thanks for this.

@saratvemulapalli
Copy link
Member Author

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 74f7ddd
Log 463

Reports 463

@dblock
Copy link
Member

dblock commented Sep 2, 2021

Should this be a default implementation in the calling code, so we wouldn't have to check in a copy of this in all projects?

@saratvemulapalli
Copy link
Member Author

Should this be a default implementation in the calling code, so we wouldn't have to check in a copy of this in all projects?

Good question. Let me know your thoughts.
The thought process is that the bwctest.sh file will define all the bwc tests the repository needs. And each repo/branch could configure it to run with few/all the tests if they need. This file enables that configuration.

That said we have 2 options:

  1. Have all repositories define bwctest.sh, make it unambiguous for any body to hook up to bwc testing.
  2. Define a default mechanism that would be called like (./gradlew bwctest) and any repository who wishes to have it custom they could define bwctest.sh.

I am leaning towards 1 (for the short term):

  • Its clear for repository owners and no magic involved.
  • While repositories are onboarding to bwctest infra, we can update the test_workflow to have a default implementation.
  • Eventually we could move to 2. and add documentation for owners.

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 8a2ed95b6c2883d708251ba66bbb76d20dc1c703

@opensearch-ci-bot
Copy link
Collaborator

❌   DCO Check Failed 8a2ed95b6c2883d708251ba66bbb76d20dc1c703
Run ./dev-tools/signoff-check.sh remotes/origin/main 8a2ed95b6c2883d708251ba66bbb76d20dc1c703 to check locally
Use git commit with -s to add 'Signed-of-by: {EMAIL}' on impacted commits

Signed-off-by: Ubuntu <ubuntu@ip-172-31-42-176.us-west-2.compute.internal>
Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com>
@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 7d8ae8d

@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 7d8ae8d

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 8a2ed95b6c2883d708251ba66bbb76d20dc1c703

@saratvemulapalli
Copy link
Member Author

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 7d8ae8d

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Check success 7d8ae8d
Log 495

Reports 495

@dblock
Copy link
Member

dblock commented Sep 8, 2021

Why do we need a custom .sh script that just calls gradle? Shouldn't this be the default for any Gradle project coming from opensearch-build?

@saratvemulapalli
Copy link
Member Author

Closing this PR.
Had a chat with @dblock , It makes sense to have a default bwctest.sh script in opensearch-build.

@saratvemulapalli saratvemulapalli deleted the bwc-snapshots branch September 15, 2021 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants