[ https://issues.apache.org/jira/browse/BEAM-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17548984#comment-17548984 ]
Danny McCormick commented on BEAM-11197: ---------------------------------------- This issue has been migrated to https://github.com/apache/beam/issues/20594 > Review Jenkins Java Test Jobs / Configurations > ---------------------------------------------- > > Key: BEAM-11197 > URL: https://issues.apache.org/jira/browse/BEAM-11197 > Project: Beam > Issue Type: Improvement > Components: build-system, sdk-java-core > Reporter: Tyson Hamilton > Priority: P3 > Labels: Clarified, Done > > The Java test jobs in Jenkins have been growing organically over time and > need to be reviewed to ensure they're balancing appropriate coverage, using > reasonable resources (e.g. infra costs, time), and are following a sane > testing strategy: > * naming is uniform and predictable (especially for PR phrases) > * postcommit monolith is broken down into individual jobs to improve > balancing across jenkins nodes > * old jobs are removed from Jenkins (e.g. [1, 2]) > * > [README.md|https://github.com/apache/beam/blob/master/.test-infra/jenkins/README.md] > file is updated > > [1]: > [https://ci-beam.apache.org/job/beam_PostCommit_Java11_Examples_Dataflow_Portability/] > [2]: > [https://ci-beam.apache.org/job/beam_PostCommit_Java11_ValidatesRunner_PortabilityApi_Dataflow/] > > -- This message was sent by Atlassian Jira (v8.20.7#820007)