kw2542 commented on a change in pull request #15169:
URL: https://github.com/apache/beam/pull/15169#discussion_r670039102



##########
File path: .test-infra/jenkins/README.md
##########
@@ -89,6 +89,7 @@ Beam Jenkins overview page: 
[link](https://ci-beam.apache.org/)
 | beam_PostCommit_Py_VR_Dataflow_V2 | 
[cron](https://ci-beam.apache.org/job/beam_PostCommit_Py_VR_Dataflow_V2/), 
[phrase](https://ci-beam.apache.org/job/beam_PostCommit_Py_VR_Dataflow_V2_PR/) 
| `Run Python Dataflow V2 ValidatesRunner` | [![Build 
Status](https://ci-beam.apache.org/job/beam_PostCommit_Py_VR_Dataflow_V2/badge/icon)](https://ci-beam.apache.org/job/beam_PostCommit_Py_VR_Dataflow_V2)
 |
 | beam_PostCommit_Py_ValCont | 
[cron](https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont/), 
[phrase](https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont_PR/) | `Run 
Python Dataflow ValidatesContainer` | [![Build 
Status](https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont/badge/icon)](https://ci-beam.apache.org/job/beam_PostCommit_Py_ValCont)
 |
 | beam_PostCommit_Python_VR_Flink | 
[cron](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Flink/), 
[phrase](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Flink/) | 
`Run Python Flink ValidatesRunner` | [![Build 
Status](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Flink/badge/icon)](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Flink)
 |
+| beam_PostCommit_Python_VR_Samza | 
[cron](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Samza/), 
[phrase](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Samza/) | 
`Run Python Samza ValidatesRunner` | [![Build 
Status](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Samza/badge/icon)](https://ci-beam.apache.org/job/beam_PostCommit_Python_VR_Samza)
 |

Review comment:
       Really nice catch! Let me fix both of them. 




-- 
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]


Reply via email to