[jira] [Updated] (INFRA-11610) Jenkins pre-commit coverage in a GitHub mirror

["Chris Lambertus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-11610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambertus updated INFRA-11610:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

The long and short of it is that we don't know. We're extremely short staffed and this hasn't been a priority. Sorry for the lack of response, though.. What would you need in order to troubleshoot or test this further? 

> Jenkins pre-commit coverage in a GitHub mirror
> ----------------------------------------------
>
>                 Key: INFRA-11610
>                 URL: https://issues.apache.org/jira/browse/INFRA-11610
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Github, Jenkins
>            Reporter: Davor Bonaci
>
> In Apache Beam, we use GitHub pull requests to review code, which integrates pre-commit test results from Jenkins.
> So far, we have had just one pre-commit Jenkins job: "beam_PreCommit_MavenVerify". Its result was integrated into GitHub pull request UI correctly.
> We've recently added the second pre-commit job: "beam_PreCommit_RunnableOnService_GoogleCloudDataflow".
> The link from GitHub UI automatically started pointing to this second pre-commit job, and no longer integrates the result from the first pre-commit job. On the other hand, Jenkins seems to be running both jobs correctly and concurrently.
> Ideally, we'd like to have the test results from both jobs integrated into GitHub UI as two separate lines/results.
> Would something like this be possible?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)