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
HDDS-3784. Use matrix build for integration test #1063
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1063 +/- ##
============================================
+ Coverage 69.38% 69.40% +0.02%
- Complexity 9104 9111 +7
============================================
Files 961 961
Lines 48121 48121
Branches 4676 4676
============================================
+ Hits 33387 33397 +10
+ Misses 12514 12509 -5
+ Partials 2220 2215 -5 Continue to review full report at Codecov.
|
@adoroszlai I like this matrix approach. Its much cleaner now. Thanks for working on this! Can you merge the latest master with this branch since recent commits involve changes in the workflow? It will be good to see another run here before merging. Thanks! |
Thanks @vivekratnavel for the review. I have merged latest workflow-related changes from |
@adoroszlai Thanks for the merge! The CI run looks good. I am merging it now. |
Thanks @vivekratnavel for reviewing and merging it. |
What changes were proposed in this pull request?
Reduce code duplication in Ozone's GitHub Actions workflow definitions by using matrix build for integration tests instead of individual jobs.
https://issues.apache.org/jira/browse/HDDS-3784
How was this patch tested?
Verified that multiple integration test runs with different profiles were executed in parallel:
https://github.com/adoroszlai/hadoop-ozone/runs/761852962
https://github.com/adoroszlai/hadoop-ozone/runs/761852971
They each uploaded separate artifacts.
Verified that coverage check waits for all of these.