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/03/09 08:05:40 UTC
[jira] [Created] (INFRA-11414) Enable continuous integration for
Beam (incubating)
Davor Bonaci created INFRA-11414:
------------------------------------
Summary: Enable continuous integration for Beam (incubating)
Key: INFRA-11414
URL: https://issues.apache.org/jira/browse/INFRA-11414
Project: Infrastructure
Issue Type: Task
Components: Github, Jenkins
Reporter: Davor Bonaci
Could we get both Travis-CI and Jenkins pre-commit coverage enabled for Apache Beam (incubating)?
We'd like to mimic the behavior of other projects, like Apache Thrift. For example, this pull request [1] to their GitHub repository has Travis, Jenkins, and AppVeyor pre-commit coverage enabled. We don't need AppVeyor at this time.
Travis: the configuration is already part of our repository, including .travis.yml and its dependencies. This coverage is working on our private forks.
Jenkins: we have a job on Apache Jenkins instance [2], which we'd use both for regular coverage and pre-commit coverage. It should already be configured to run on pull requests, but we have no way of testing this.
Could you please assist?
[1] https://github.com/apache/thrift/pull/927
[2] https://builds.apache.org/job/beam_MavenVerify/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)