You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2016/04/07 00:04:25 UTC
[jira] [Created] (INFRA-11610) Jenkins pre-commit coverage in a
GitHub mirror
Davor Bonaci created INFRA-11610:
------------------------------------
Summary: Jenkins pre-commit coverage in a GitHub mirror
Key: INFRA-11610
URL: https://issues.apache.org/jira/browse/INFRA-11610
Project: Infrastructure
Issue Type: Task
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 corrently 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)