You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 19:54:05 UTC

[GitHub] [beam] damccorm opened a new issue, #20839: Make Jenkins job triggers predictable.

damccorm opened a new issue, #20839:
URL: https://github.com/apache/beam/issues/20839

   AFAIK Jenkins jobs have up to three different names.
    
   1. The job name stem, e.g. "PostCommit_Java_VR_Dataflow_V2". This is defined in the source file "job_PostCommit_Java_ValidatesRunner_Dataflow_V2.groovy" (I assume the "job_" prefix is arbitrary; I'm not sure why we use a filename prefix instead of a proper subfolder). In Jenkins, the job name is prefixed by "beam_" (I assume for historical reasons) on Jenkins and postfixed for variants like "_cron" or "_phrase". 
   2. The Github comment trigger, e.g. "Run Java Dataflow V2 ValidatesRunner"
   3. The job name displayed on Github, e.g. "Google Cloud Dataflow Runner V2 Java ValidatesRunner Tests"
    
   The latter two seem redundant.
    
   
   Imported from Jira [BEAM-12412](https://issues.apache.org/jira/browse/BEAM-12412). Original Jira may contain additional context.
   Reported by: ibzib.


-- 
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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org