[jira] [Commented] (BEAM-12572) All beam examples should get continuously exercised on at least 2 runners

["Benjamin Gonzalez (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436094#comment-17436094 ] 

Benjamin Gonzalez commented on BEAM-12572:
------------------------------------------

Hi [~tvalentyn] , I've started to do some analysis for this issue.
I've found that most examples with unit tests for Java and Python are currently running on DirectRunner in PreCommit jobs, while the examples with integration tests are running on Dataflow in PostCommit jobs.
I want to ask you about the best approach to complete this task.
My first idea is to create a Jenkins job per language and runner, like the existing [PreCommit_Java_Examples_Dataflow|https://ci-beam.apache.org/job/beam_PreCommit_Java_Examples_Dataflow_Cron/lastCompletedBuild/testReport/org.apache.beam.examples/]  (Currently is running just for two integration tests), but I'm not sure if those new jobs should run both unit and integration tests related to examples.
I've created [this|https://docs.google.com/spreadsheets/d/1WtdIZZr-cYF1FqVq7ak4bsDax9occ-eHwz5iw310GHo/edit?usp=sharing] sheet to track coverage of examples per language and runner.

> All beam examples should get continuously exercised on at least 2 runners
> -------------------------------------------------------------------------
>
>                 Key: BEAM-12572
>                 URL: https://issues.apache.org/jira/browse/BEAM-12572
>             Project: Beam
>          Issue Type: New Feature
>          Components: testing
>            Reporter: Valentyn Tymofieiev
>            Assignee: Benjamin Gonzalez
>            Priority: P3
>
> Sometimes our examples become broken without us noticing. For example, see: https://lists.apache.org/thread.html/r45340bbee91a6caf798fe62d24388f645f8792cc7506351fd66adec3%40%3Cdev.beam.apache.org%3E
> We should test our examples better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)