damccorm opened a new issue, #20594:
URL: https://github.com/apache/beam/issues/20594
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/](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/](https://ci-beam.apache.org/job/beam_PostCommit_Java11_ValidatesRunner_PortabilityApi_Dataflow/)
Imported from Jira
[BEAM-11197](https://issues.apache.org/jira/browse/BEAM-11197). Original Jira
may contain additional context.
Reported by: tysonjh.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
