www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Takamori (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11610) Jenkins pre-commit coverage in a GitHub mirror
Date Wed, 13 Apr 2016 20:58:25 GMT

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

Daniel Takamori commented on INFRA-11610:
-----------------------------------------

This job (on the Jenkins side) could be changed to trigger for any change to Github.  Would
this suffice for what you are looking for?

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

Mime
View raw message