[
https://issues.apache.org/jira/browse/BEAM-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227667#comment-17227667
]
Tyson Hamilton commented on BEAM-11197:
---------------------------------------
Another question, for my later thinking,
* Why do these builds exist, as well as those in the 'postCommit' task in the
parent google-cloud-dataflow-java/build.gradle:
** runners/google-cloud-dataflow-java/examples/build.gradle (otherwise empty
directory)
** runners/google-cloud-dataflow-java/examples-streaming/build.gradle
(otherwise empty directory)
They seem to similarly configure tests to run the examples using various groovy
files,
* .test-infra/jenkins/job_PostCommit_Java_Dataflow_Examples_Java11.groovy
* .test-infra/jenkins/job_PreCommit_Java_Examples_Dataflow.groovy
* .test-infra/jenkins/job_PreCommit_Java_Examples_Dataflow_Java11.groovy
> 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: P2
>
> 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.3.4#803005)
