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

Enable golang e2e test in CI #85

Merged
merged 1 commit into from
Jun 6, 2024
Merged

Conversation

daisy-ycguo
Copy link
Collaborator

Description

Enable golang e2e test in CI

Issues

n/a

Type of change

List the type of change like below. Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds new functionality)
  • Breaking change (fix or feature that would break existing design and interface)

Dependencies

n/a

Tests

CI test

@daisy-ycguo daisy-ycguo force-pushed the goe2e branch 5 times, most recently from c4bdcf8 to e0ad722 Compare June 6, 2024 10:09
Signed-off-by: Yingchun Guo <[email protected]>
@daisy-ycguo
Copy link
Collaborator Author

@irisdingbj If you want to add e2e tests for microservices-connector, please follow my guidance in scripts/e2e/go-test.sh and add your logic in three functions install_gmc, validate_gmc and cleanup_gmc. I've tested that any changes under the folder microservices-connector will trigger the go-e2e workflow. Please help to review and merge this PR. Then you can continue your development base on it. Thank you.


jobs:
go-e2e:
runs-on: k8s
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks for the support for gmc e2e. Since we need support Gaudi as well, possible to make this runner setting as an Env Var? then in the gmc test script we can leverage this env var to select and deploy related manifests.

- name: Install modules
run: |
echo "should_cleanup=true" >> $GITHUB_ENV
.github/workflows/scripts/e2e/go_test.sh install_gmc
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we use separate script for different go project? In this case, CI can be clear which part fails. Based on that, I will prefer naming it as gmc_test.sh. Thoughts?

@irisdingbj
Copy link
Collaborator

Thanks for the support! Let's merge this first and we can address the env var and filename in follow up PR.

@irisdingbj irisdingbj merged commit bc9abac into opea-project:main Jun 6, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants