In GHA we also used a third-party action (EnricoMi/publish-unit-test-result-action) to do the same thing, and archive the JUnit report when test failure, but Python GHA tests currently does not have this functionality.
We should preserve the ability to check which test has failed without digging into the raw log for Python test as well, then we can teardown Jenkins Python tests without introducing regression. We probably can use the same action used for Java (EnricoMi/publish-unit-test-result-action) since its documentation says it supports Python as well.
Workflows include
Python PreCommit jobs (including the large PreCommit, PreCommit Coverage, PreCommit DataFrame, etc)
Python PostCommit jobs
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Abacn
commented
1 year ago
What needs to happen?
in Jenkins we have access to test report of both Java and Python tests, e.g.
https://ci-beam.apache.org/job/beam_PreCommit_Java_Cron/lastCompletedBuild/testReport/
https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/lastCompletedBuild/testReport/
In GHA we also used a third-party action (EnricoMi/publish-unit-test-result-action) to do the same thing, and archive the JUnit report when test failure, but Python GHA tests currently does not have this functionality.
We should preserve the ability to check which test has failed without digging into the raw log for Python test as well, then we can teardown Jenkins Python tests without introducing regression. We probably can use the same action used for Java (EnricoMi/publish-unit-test-result-action) since its documentation says it supports Python as well.
Workflows include
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components