Review Jenkins Java Test Jobs / Configurations

[damccorm]

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 file is updated

 

 

 

Imported from Jira BEAM-11197. Original Jira may contain additional context.
Reported by: tysonjh.