www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-11414) Enable continuous integration for Beam (incubating)
Date Wed, 09 Mar 2016 08:15:41 GMT

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

Daniel Gruno updated INFRA-11414:
    Status: Waiting for user  (was: Waiting for Infra)

A bit confused here :)
If all you currently want is having travis enabled for your repo(s), we can get you set up
pretty quickly.

> 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

View raw message